26062019 Better — Alura Tnt Jenson A Demanding Client

By Day 12, the relationship had shifted. The demanding client was no longer a source of friction. They were a source of truth. The final week was a sprint. Sleep was scarce. Coffee was abundant. But something incredible happened: the team started finishing ahead of the client’s demands.

The demanding client wanted none of that. By Day 3, the client had rejected the initial wireframes. By Day 4, they had flown in their own UX consultant to challenge TNT’s architecture. By Day 5, Jenson had his first (and only) public argument with a client stakeholder over unit testing protocols. alura tnt jenson a demanding client 26062019 better

| Metric | Average Project | Project 26062019 | | :--- | :--- | :--- | | Timeline | 14 weeks | 4 weeks | | Revision cycles | 6 | 12 | | Client comms (emails/calls) | 240 | 850 | | Critical bugs at launch | 4 | 1 | | Post-launch support tickets (30 days) | 112 | 31 | | Team burnout rate | 20% | 60% (temporary) | | Client lifetime value | $180k | $1.2M | By Day 12, the relationship had shifted

In the world of high-stakes project management and creative production, the phrase “demanding client” often carries a negative connotation. It conjures images of endless revision loops, scope creep, and strained relationships. However, every once in a while, a project comes along that redefines the term entirely. The final week was a sprint

It was chaos.