Ways to Work
How a project runs with me
I keep projects calm and practical. We make sense of where you are, choose what matters most, and move forward one useful step at a time.
Here’s how that usually looks.
A Typical Project Timeline
1) Intro call
A 20-minute chat to understand your goals, constraints, and timelines. If the situation is complex, I’ll suggest a follow-up to dig in a little more.
What you get: a short email with my understanding of the problem, likely approach, and next step.
2) Proposal and scope
After the call I prepare a quote. Sometimes that covers an initial scoping mini-engagement (a few focused meetings). For bigger pieces of work, I share a scoped proposal you can treat as the contract.
What’s inside the proposal: outcomes, scope and assumptions, timeline, cadence, deliverables, and fees. I keep it plain English.
3) Discovery workshops
Once we start, I run a short series of remote meetings to learn how things work today and what “good” looks like. I mix methods depending on the context:
Targeted questionnaires to capture goals, roles, and pain points
System and process mapping (from sticky-note sketches to a clean diagram)
Workflow and handover reviews (where things stall, who decides)
Light data and KPI review (what’s measured, what should be)
Tooling review (what stays, what integrates, what to stop using)
Typical artefacts created here: current-state map, notes from interviews, initial risks/assumptions, a draft outcomes list.
4) Sense-making and design
I translate discovery into a simple plan and working models. Depending on the project, that can include:
A one-page plan with priorities, owners, and next steps
Future-state process or integration diagram (often in Kumu or Miro)
Role clarity pieces: role scorecards, RACI + handovers, and a light comms cadence
KPI set and targets with a data-capture plan and a simple dashboard prototype
Software advisory and evaluations (for example, scheduling, CRM, forecasting, analytics)
A “write your own job description” exercise when leadership focus is part of the goal
5) Draft deliverables and review
I share the draft outputs for feedback. We’ll meet to walk through decisions, tighten wording, and confirm owners and timelines.
End of planning: you leave this stage with agreed deliverables you can implement yourself or hand to a developer/third party.
6) Implementation and support (optional)
If you want help landing the plan, I stay involved. Support ranges from light guidance to hands-on delivery:
Regular check-ins to keep momentum and adjust
Managing delivery schedules and dependencies
Coordinating with third-party providers and translating requirements
Implementing small, contained changes myself where it makes sense
Examples of Deliverables
(Clients often mix and match these)
-
Role scorecards and expectations
RACI with handover checklist
Comms cadence guide and decision log template
Career/role coaching using the GROW framework
-
Current and future-state maps
One-page plan with next 3–5 actions
Integration roadmap and developer-ready brief
-
KPI definitions and targets
Data-capture plan and dashboard prototype
-
Software advisory (e.g., forecasting, CRM, workflow)
Evaluation notes and adoption steps
Marketing/SEO brief for tender where relevant
"I’m no longer the default for every decision. The team knows what ‘good’ looks like and I have more time to work on the business.”
What to expect from me
Clear communication, simple documents you’ll actually use, and a steady rhythm that keeps progress real without adding noise. I stay practical, use your existing tools where possible, and keep people and constraints in view.
OR