No Requirements. No Timeline. No Visibility.
Have you ever walked into a room full of very smart, high-value people and realized no one could answer a basic question?
Not because they didn’t want to. Because six months in, there was still no idea of what was done.
A future-forward demo had been presented and greenlit. Now, a room full of product, development, and design leads had gathered to figure out what was actually being built.
What they had: a wishlist and a few fragmented wireframes.
That was my first day on the team.
The dev team tried to cobble something together from that demo, a demo that wasn’t grounded in any of the systems that would support it. No clear direction. No timeline. No roadmap. Requirements? What’s that?
The strategist didn’t know what she didn’t know and couldn’t tell the business where their app stood.
What they did was productivity theater. Hours spent in “planning” meetings. A constant loop of conversation that felt like progress but produced nothing.
Six months in, the UX’r designing the screens had no idea how far behind they were.
No transparency in, no transparency out.
The UX’r came to me, worried. The design lead told me they had been frozen out — with no visibility into what the team was doing and no way to support them.
Then I looked at what actually existed: wires and feature wishlists. Nothing was tied to a timeline. Nothing was tied to a requirement. Nothing was tied back to the systems supporting it.
Now I was supposed to help a team meet goals that had never been set.
Then Product stepped in.
They built a real timeline and implemented phased feature delivery. The work that should have existed six months ago finally started to appear.
The strategist was pulled back in. So was I. Not as partners — as support for a plan we hadn’t created. She didn’t like the structure. At least it gave me somewhere to start.
The shift.
The more visibility I brought to the project — the more meetings I joined, the more overviews I gave — the more the door slowly closed — the strategist who’d been happy to have me there started routing around me.
This is what happens when you’re too good at the job someone else was supposed to do. They no longer control the narrative. You get managed out.
Does this sound familiar?
Maybe you were the designer who found out you were behind.
Maybe you were the person who walked in on day one and saw the gaps.
Maybe you were one of the developers in the room who had been waiting for a handoff.
All three of you are living in the same broken system. The dysfunction isn’t the fault of any one person. The structure allowed six months to pass without a single visible deliverable and labeled it “strategy.”
How to break the cycle.
If you’ve been on the same screen, working on minute details for more than a few days without the full picture mapped, you are blocked. Not because something is broken — because the full picture must exist before the details do. Raise the flag before it becomes a fire.
The visibility checkpoint
Once a week. Fifteen minutes. Check in.
Send your design lead a short update in whatever channel you already use:
Completed: What’s done and ready for review
In flight: What you’re actively working on
Up next: What you’re moving to after this
Blocked: What you’re waiting on before you can move forward
That’s it. Four lines. It doesn’t need to be long — it does need to be consistent.
This isn’t a status report for leadership. It’s a lifeline between you and the person whose job it is to support you. The design lead can’t advocate for time, resources, or direction if they don’t know what you’re facing.
Visibility doesn’t require a new system. It requires one message, sent before anyone has to ask.
The Operating Gap diagnoses the systems that bury good work. If this landed, forward it to the person who needs it, or send me your story.