Consultation · Ongoing
Project Management
Duration
Ongoing
Engagement
Project Management
Starts with
A written brief
Status
Taking bookings
(01) Our take
Project management is the discipline everyone underestimates until they’ve watched a good engineering team miss an important date because nobody owned the seam between design, engineering, and the outside world. The work isn’t glamorous, and on most teams it’s donated by whoever has the least leverage to refuse — usually the engineering lead, who then ships less code.
We embed a senior operator into your delivery cadence for the length of the engagement. They own the sprint rhythm, the written updates, the risk register, and the stakeholder conversations that your internal team would otherwise have to context-switch into every Thursday afternoon. They don’t run agile ceremonies for the sake of the ceremony; they run them when they’re useful and skip them when they aren’t.
We work in your tools. If your team lives in Linear, we live in Linear. If it’s Jira, it’s Jira. We’re not here to introduce a new system; we’re here to run the one you’ve already got, properly. The output is a steady cadence of written updates your stakeholders can actually read, a clean backlog your team can actually trust, and a risk register that means something because it gets looked at.
This engagement is a retainer, not a project. We quote it monthly and either side can walk with 30 days’ notice. We’d rather you keep us because we’re useful than because the contract makes it hard to leave.
(02) Is this for you
When to pick this
- Your engineering lead is spending more than a day a week on coordination instead of code.
- You’re running a multi-vendor or multi-team build and nobody owns the seams between them.
- Stakeholders outside the team don’t know what’s shipping or when, and meetings aren’t fixing it.
- You’ve tried a junior PM and discovered the problem needs more seniority than the role attracts.
When not to pick this
- You already have a strong PM. We’d be a second cook in a one-cook kitchen.
- The work is a small, well-defined build with one engineer. A shared doc and a Friday check-in is cheaper and just as effective.
- What you actually need is engineering leadership, not coordination. That’s a different hire.
(03) Process
Week by week
Week 1
Embed, shadow standups, read the backlog, meet stakeholders.
Week 2
First sprint plan and demo cadence established.
Ongoing
Weekly written updates, sprint cadence, risk tracking, stakeholder comms.
Monthly
Retro, roadmap check, renewal or offboarding conversation.
(04) What you get
Deliverables
The headline artefact
A weekly written update that your stakeholders actually read, and a delivery cadence that stops slipping.
Alongside it
- Sprint planning & retros
- Weekly written updates
- Risk & blocker tracking
- Stakeholder communication
(05) Pairs with
Related consultations
Engagements we often run alongside or after Project Management.
Book a Project Management engagement.