Practice 01 · Project Management
There is no universally best methodology — only the right one for your kind of work. We help you choose, tailor and implement a delivery approach that makes progress visible, decisions faster and deadlines believable again.
Methodology guide
Use this as a starting point for the conversation. Real teams often blend elements — the skill is knowing which parts to keep.
A
Best for
Product and software teams building in short increments with an engaged product owner.
Cadence
Two-week sprints with planning, daily stand-up, review and retrospective.
Watch out for
Ceremony overload in small teams, or sprints used as mini-deadlines with no real learning.
B
Best for
Service, operations and support teams with a continuous flow of varied requests.
Cadence
Continuous; weekly replenishment and a monthly flow review.
Watch out for
Boards with no work-in-progress limits quickly become to-do lists that hide bottlenecks.
C
Best for
Fixed-scope, client-facing or compliance-heavy projects with clear phases.
Cadence
Phase gates with formal sign-off, milestone tracking and change control.
Watch out for
Late discovery of problems, and plans that are defended instead of updated.
D
Best for
Organisations running a mix of predictable programmes and fast-changing work.
Cadence
Stage-gated milestones on top, iterative delivery underneath.
Watch out for
Blending without rules — every team improvising its own version of the process.
What we deliver
We stay through implementation because that is where most methodology changes fail. By the end of the engagement your team will have:
01
A single front door for new work, with simple scoring so the most valuable projects start first.
02
Columns, statuses, fields and automations in your chosen tool that match the agreed process exactly.
03
A RACI for each project type so everyone knows who decides, who does and who must be informed.
04
Practical sizing techniques, capacity planning and buffers that make deadlines realistic.
05
A weekly one-page status and a monthly portfolio review leaders can read in five minutes.
Signs you need this
Engagement timeline
W1–2
Interview leads, review live projects and score methodology fit.
W3
Agree the method, roles and tool configuration with sponsors.
W4–6
Build boards, templates, intake forms and the reporting pack.
W7–10
Run live projects through the new system and coach project leads.
W11–12
Finalise the playbook, train owners and schedule the check-in.
No. Certifications are useful, but most teams succeed with a clear process, good tools and coaching for the people already leading projects. We help you identify when a dedicated project role is worth adding.
The one your team will actually use. We have configured Asana, ClickUp, Jira, Trello, Monday.com and Notion many times. Process comes first; the tool is configured to match it.
Yes. A recovery review takes a few days: we re-baseline scope, surface hidden dependencies, agree a realistic plan with stakeholders and set up tight weekly tracking until the project is stable.
We agree a small set of measures at the start — for example on-time milestone rate, cycle time, work-in-progress and the share of projects with a current status — and report against them throughout.
Tell us about the projects that keep slipping. We will suggest a practical first step during a free 30-minute call.
