Strategy decks are easy. The hard part of any engagement is the gap between the slide that says "phase 2 execution" and the moment, three months later, when the system is actually live, the user is actually using it, and the post-mortem shows the numbers we said we'd hit. That gap is where I spend my days.
My role at Digital It Move is the unglamorous one. I take the architecture, the commitments, the success metrics that our engineers and strategists have agreed with the client, and I make them real on time, on scope, on budget, and with a level of predictability that lets the client actually plan around us. When we are doing my job well, nobody notices. When we are doing it badly, everyone does.
The principles I run my projects by
I am wary of elaborate project management methodology. Most of it is theatre. The handful of habits below have, over the years, accounted for almost every successful engagement I've been part of. They are not original to me, but they are not optional either.
1. The definition of done is written, signed, and dated.
Before any line of code is shipped, before any cable is run, before any migration is rehearsed the client and we agree, in writing, what "done" means. The metrics. The acceptance criteria. The out-of-scope items. The rollback conditions. This is the document we measure ourselves against for the rest of the engagement. Ambiguity at this stage costs weeks later. We refuse to pay that bill on the client's behalf.
2. The plan is rehearsed, not just approved.
Every non-trivial cutover a SOC migration, a cloud move, an office relocation, a boardroom re-engineering gets a full dry run in a lab environment before the live event. The cost of rehearsal is a small number of engineering hours. The cost of skipping rehearsal is a public incident. We have learned this more than once.
3. Risk is named, not hidden.
Every project has a risk register, updated weekly, with the active risks reviewed at every steering call. We name the risks before they become issues. We do not bury them to keep a Gantt chart looking clean. The cleanest Gantt chart is the one that's been quietly re-baselined three times because nobody raised their hand.
Predictability isn't a personality trait. It's a process. The project manager's job is to make sure the process is followed even when especially when the team is tired, the deadline is tight, and the easier thing would be to skip a step. Deepak Paraye
How I actually run an engagement
People sometimes ask me what a typical week looks like. The honest answer is that the visible work the steering decks, the status updates, the escalation emails is a small fraction of it. The rest is the quiet, mostly invisible craft of keeping a complex piece of work on its rails. For those who find that useful, here is the rough shape.
Pre-kickoff (the week before anything starts)
Confirm the scope document is signed. Confirm every named stakeholder has been introduced, with their role and their preferred contact channel. Walk the engineering lead through the dependency map. Identify the two or three decisions that, if delayed, will block the project and get those pre-scheduled with the right decision-makers.
Week 1 establish the rhythm
Set the cadence: standup time, weekly demo slot, weekly steering call. Set the comms norms: where the work is tracked, where the risks are logged, where the decisions are recorded. Most project failure is not engineering failure; it is comms failure that surfaces as engineering failure. We invest disproportionately in this first week.
Mid-engagement keep the rails on
Track the burndown against the original baseline, but treat the baseline as a living document. Catch scope creep early usually in the third or fourth week, when the client sees progress and starts to add "while you're at it" requests. Most of these are reasonable. None of them are free. The discipline is to acknowledge them, price them, and decide together never to absorb them silently.
Closeout protect the handoff
The final two weeks of an engagement are when most of the value either gets locked in or leaks away. Documentation, training, runbook handover, success metrics report, the post-engagement support plan. I treat closeout as a deliverable in its own right, with its own checklist, not as an afterthought after the last deployment.
What I would tell a new project manager on our team
The single most useful thing you can do, in your first month, is read every post-mortem we have from the last three years. Not to find who to blame. To find the patterns. The patterns are where the real lessons live. They are also, almost always, smaller and more boring than the dramatic incident that triggered the post-mortem in the first place. The drama is in the customer call. The lesson is in the missed status update three weeks earlier.
The other thing I tell new PMs is this: your engineers will not always tell you when they are behind. Not because they are hiding it usually because they genuinely believe they can recover in the next sprint, and they don't want to make a fuss. Your job is to make it safe for them to surface bad news early. That starts with how you respond to the first bit of bad news they bring you. Respond well, and they will bring you more. Respond badly, and you will find out on the day of the cutover.
On the work itself
I joined Digital It Move because the brief the firm writes for itself is the brief I would want my own clients to write. Senior delivery. Integrated practices. Outcome-priced where possible. You own what we build. Those are not slogans to me they are the operating conditions under which good project management is possible. When the team around you is operating on those terms, the project manager's job is mostly to stay out of their way and keep the bureaucracy from slowing them down. That is the good version of my job. It is also, I should note, the version I get to do most days, which is why I am still here.
If you are reading this because you are considering bringing us in for a project thank you for taking the time. The brief you send us will land with a real PM, who will read it carefully, will probably push back on at least one assumption in it, and will set up the engagement to give us the best possible chance of shipping something you'll be proud to put your name on. That is the standard we hold ourselves to, and it is the only one I know how to work to.
I look forward to the project.