Stop managing million-dollar projects while leaving your own life to chance.
Imagine walking into the Monday morning executive meeting. A project manager stands before the leadership team to present the status of a critical initiative.
“Where’s the project charter?”
“I never wrote one.”
“What’s the timeline?”
“We’re figuring it out as we go.”
“What are the milestones?”
“We’ll know them when we get there.”
“What risks have you identified?”
“I haven’t really thought about them.”
“How will you measure success?”
“I just hope everything works out.”
That meeting wouldn’t last five minutes.
No board would approve it, no investor would fund it, no organization would entrust millions of dollars to someone managing a project with nothing more than optimism and good intentions.
Yet many of us manage the most important project we’ll ever own exactly that way.
Our lives, our finances, our careers, our relationships, our families, our health, our legacy.
We wake up, stay busy, meet deadlines, and hope that somehow everything will eventually add up to the future we imagined. We mistake activity for direction, and motion for progress.
Here’s the uncomfortable truth: every successful project has a project manager because unmanaged projects rarely collapse overnight. They drift.
Budgets quietly expand, deadlines gradually slip, small issues go unaddressed until they become expensive problems. By the time the postmortem happens, the opportunity to change the outcome has already passed.
The same thing happens in life.
Very few people wake up at 45 and suddenly become financially unstable. More often, it’s the cumulative result of years without planning, measurable milestones, regular reviews, or disciplined execution.
The greatest project you’ll ever manage isn’t the one on your laptop. It’s the one staring back at you in the mirror.
The Charter You Never Wrote
Every project starts with a charter, a document that answers three questions before a single task begins: What are we building? Why does it matter? What does success look like?
Ask most people what their financial “charter” is, and you’ll get a shrug, or something vague like “I want to be comfortable” or “I want to retire someday.” That’s not a charter. That’s a wish.
A real charter is specific enough to measure against. Not “build wealth”, but “$500k net worth by 45, debt-free, owning property in two countries, funding my kids’ education without loans.” Not “send money home”, but “fund my sister’s business launch by year three, then transition to advisory, not ongoing subsidy.”
For diaspora families especially, the charter question gets skipped because two lives are running in parallel, the one here and the one back home, and nobody ever sat down and defined what success looks like across both. You’re managing a multi-country project with a single-country plan. That’s not a minor oversight. That’s the project failing at the design phase.
Scope Creep Is Why You’re Broke
In project management, scope creep is the slow, unauthorized expansion of a project beyond its original goals, and it’s one of the most common reasons projects blow their budgets and timelines. Someone asks for “just one more feature.” Nobody says no. Six months later, the project that was supposed to take three months is still going, and nobody can point to the moment it went sideways.
Your finances have scope creep, too. You just don’t call it that. You call it a nicer car. A bigger apartment. Dinners out that used to be occasional and are now just on Tuesdays. None of these decisions, on their own, sank you. That’s exactly the point: scope creep never looks like a single bad decision. It looks like a hundred reasonable ones, none of which anyone charged you a change-order fee for.
In a well-run project, every scope change gets evaluated against the original charter: does this serve the goal, or does it just feel good right now? Your bank account deserves the same discipline. Before the next “yes,” ask what a project manager would ask: does this expansion serve the charter, or are we just letting the project drift?
Milestones, Not Resolutions
January 1st isn’t a launch date. It’s a Waterfall mistake.
Waterfall project management, plan everything up front, execute in a straight line, don’t deviate, fails constantly in the real world because reality doesn’t hold still for a year-long plan. That’s why most modern project teams have moved to iterative methods: short sprints, regular check-ins, course corrections built into the system instead of being treated as failures.
Resolutions are Waterfall. You commit to a massive, vague goal on day one, don’t check in until it’s already broken, and then feel like a failure instead of realizing the methodology was wrong from the start.
Try sprints instead. Two-week or monthly financial cycles with a real retrospective at the end: What did we actually do? What worked? What’s the adjustment for the next sprint? This isn’t corporate cosplay; it’s the difference between a plan that bends and a plan that snaps.
The Risk Register Nobody Keeps
Before any serious project begins, PM teams build a risk register, a documented list of what could go wrong, how likely it is, how bad the impact would be, and what the mitigation plan is. It’s not pessimism. It’s preparation dressed as a spreadsheet.
Most people have never written down what could derail their finances. Not vaguely worried about it, actually written it down. Job loss. A health event. A currency devaluation back home that cuts the value of a remittance in half overnight. A market downturn hits right when you need liquidity.
For diaspora families, the risk register is longer than most; you’re exposed to two economies, two currencies, two sets of political and regulatory risk, sometimes two sets of family obligations that can shift without warning. Pretending that complexity doesn’t exist doesn’t make you safer. It just means the risk shows up as a crisis instead of a line item you already planned for.
The Retrospective You Owe Yourself
The single habit that separates high-functioning project teams from chaotic ones isn’t better planning; it’s the retrospective. The regular, unemotional look back: what happened, what we’d do differently, what we’re carrying forward.
Most people never do this with money. They either avoid looking at all, or they look only when something’s on fire. There’s no quarterly review. No honest accounting of the sprint that just ended.
You don’t need a fancy system. You need a recurring meeting with the one stakeholder who’s easiest to ignore: yourself.
The Reframe
None of this requires new information. You already know how to run a project; you’ve watched it done well, or badly, at work. The gap isn’t knowledge. It’s an application. Nobody ever told you the same discipline applies here, to the project that actually matters most.
Write the charter. Watch the scope. Run the sprints. Keep the risk register. Hold the retrospective.
Your life was always the biggest project you’ll ever manage. Start treating it like one.
The more I learn, the more I discover how little I know. Until the next issue, Coach MO.
