Perla › Manifest › a project manager
Manifesting a Project Manager every blocker named by noon
This role looks, from outside, like a chart with coloured bars. From inside it's a standup kept short, a blocker named honestly instead of hidden, and a plan that flexes without falling apart when something goes sideways. This script is the actual running of it.
- A full script for a project manager, written in the present tense and ready to read tonight.
- Shorter versions — one for falling asleep, one for the morning, and one line to carry with you.
- How to use it: A standup you expect to be tense, or the evening before a stakeholder update where the news isn't all good, is exactly when this is useful.
- The common mistake: Letting a blocker sit unnamed for a few days, hoping it resolves itself, instead of raising it the moment it's noticed — silence is what turns a small dependency into a missed deadline.
The script
Read it slowly, in the present tense, as though it has already happened. It is written to be spoken aloud, but silently is fine.
Standup's at nine and I keep it to fifteen minutes, same as always — what got done, what's next, what's stuck. Someone flags a dependency that's running late from another team, and instead of letting it sit quietly until it becomes a crisis, I name it out loud, note it, and go find the person who can actually unblock it right after. That conversation takes ten minutes and solves what could've cost us three days if it had surfaced next week instead of today. I update the plan, not dramatically, just an honest shift of two tasks, and flag the change in the shared doc so nobody's surprised later. Midday I write the stakeholder update, short and plain, no padding to make slower progress look faster than it is. One task on the board is genuinely ahead of schedule, so I let that be visible too, not just the risks. In the afternoon I sit with a task that's stuck and help unpick why, rather than just asking for a faster estimate. By five the board's honest, the blocker's cleared, and tomorrow's standup already has less to report because today's problems got solved today instead of carried forward.
Shorter versions
Two for the ends of the day, and one line to carry through the middle of it.
The board's updated, the blocker from this morning cleared, the stakeholder update sent and done with. Nothing's sitting quietly waiting to become a bigger problem next week. I'm not running tomorrow's standup in my head tonight — it'll run the way it always does, fifteen minutes, honest, then everyone gets back to their own work, same as today did.
I check the board before the standup, so I already know roughly what today's going to raise before anyone says it out loud. There's a dependency I'm watching from yesterday, and I'll chase it early rather than waiting for it to become urgent. The plan for today is what it usually is: name the blockers, clear what I can, keep the update honest.
Name the blocker out loud, then go find the person who can actually clear it.
How to use it
A standup you expect to be tense, or the evening before a stakeholder update where the news isn't all good, is exactly when this is useful. Dependencies chased down and honest updates sent are what actually move a project forward — a calm mindset alone moves nothing, but it's usually what makes chasing the dependency happen today instead of next week.
The mistake to avoid
Letting a blocker sit unnamed for a few days, hoping it resolves itself, instead of raising it the moment it's noticed — silence is what turns a small dependency into a missed deadline. The other trap is padding a stakeholder update to sound better than the actual state of the project, which only makes the eventual honest version harder to hear.
Questions
Does a script like this help a project actually finish on time?
No — timelines depend on the work, the team and the real dependencies, not on anything read beforehand. What it can help with is staying clear-headed enough to name problems early, which is what actually protects a deadline.
Isn't naming a blocker out loud in a standup an awkward thing to do?
It can feel that way at first, but naming it early is far less awkward than the alternative — a dependency that quietly turns into a missed deadline three weeks later.
Is it a bad sign if something needs replanning partway through a project?
No — replanning honestly, in response to real information, is normal project management. It's a different thing from a plan falling apart from being ignored.
Have this written about you
The script above is written for anyone. Perla asks about your actual situation, writes it as a present-tense narrative and reads it back to you — in a calm voice or your own, recorded once. One ritual instead of ten apps.