Built by a project manager, for project managers.

The experience behind the workbench

His work spans three complementary perspectives:

Space data systems engineering: understanding systems, interfaces, requirements and evidence.

Project management: coordinating delivery, people, suppliers, risks, schedules and budgets.

Product management: understanding needs, setting priorities and balancing technical possibilities with practical value.

Why I built PM Control Workbench

Before a review, I want to see what has changed. When a decision is questioned, I want to find the reasoning behind it. When a supplier makes a commitment, I want to know who will follow it up.

I built PMCW to keep those connections close: actions, risks, decisions and meeting notes alongside the information that explains them.

What I believe a useful tool should do

Be useful to one project manager. I’m building for individual use alongside the systems a team already has in place.

Keep the context close. I want an action to stay connected to the conversation behind it, the person responsible and the next step.

Support judgement. My aim is to make it easier to see what needs attention and why, while leaving the decision with the project manager.

Keep project information under your control. I chose a local project workspace, with explicit exports when information needs to be shared.

Shaped by space-industry experience. Built for project work.

My experience comes from space. Coordinating dependencies and following commitments through are challenges in many project environments.

I'm building PMCW for project managers who carry responsibility for delivery and need to keep the reasoning behind the work close at hand.