Blog
Three and a half days in a room fixed a startup's roadmap
A startup CEO kept calling me frustrated with his developer. We put them in a room for three and a half days, then ran a daily requirements, build, demo loop.
One of my startups had a CEO who kept calling me frustrated.
The developer wasn't delivering what he wanted, and the back-and-forth wasn't fixing it.
So we flew the developer in.
Three and a half days in a room
We sat down and worked through it for three and a half days straight.
We laid out the foundation for the product, and we found a lot of process issues along the way. Questions that had been bouncing around in messages for weeks got answered across a table.
By the end, the backlog was something the developer could actually build, and the CEO trusted it.
Then the daily loop
The room fixed the backlog. What kept it fixed was the rhythm we set up after.
The CEO sat in on standup every day at 9:30. He's still doing it, and when I spoke to him recently he said the process is really working. The designer and the business person are aligned with the developer.
They get the requirements in the door by noon. The developer gets it all done and does a build and the deployment that evening. And then they demo it the next day at standup.
If that demo passes, they release it to production.
They're releasing a new version pretty much every single day.
Requirements by noon. Build by evening. Demo at 9:30. Ship.
Why this works now
A few years ago, that loop would have been impossible. A feature took a week or two to build, so you had to batch requirements into sprints and hope you got them right.
With AI doing most of the coding, a solid developer can turn a clear requirement into a working build the same day. The build is no longer the slow part.
The slow part is knowing what to build. Requirements are now the bottleneck, and the fastest way to clear it is to get the person who has the requirements in the room with the person who builds.
What the CEO gives up
This costs the CEO real time. A standup every morning, plus being available to answer questions before noon.
Most CEOs push back on that. They want to hand the work off.
But compare it to what this CEO was doing before: getting frustrated, calling me, and waiting to see whether the developer understood. A short standup every day is cheaper than that.
How to run it
If your CEO and your developers keep talking past each other:
- Do one intense requirements session in person. A few days, same room, no laptops open on other work.
- Leave with a backlog the developer can build without asking.
- Set a daily standup the CEO attends. Short. Same time every day.
- Requirements in by midday, build that evening, demo next morning.
- If the demo passes, ship. If it doesn't, the fix goes in the next day's loop.
The first week feels intense. Once the loop is running, the frustrated phone calls stop.
I set up loops like this as a fractional CTO. If your roadmap keeps stalling between the CEO's head and the developer's screen, book a call at bry.net.
When was the last time your CEO and your developer were in the same room?