Sticky Notes, Sawdust, and Software: The Couple’s Guide to Project Management

On any given evening, Katherine Ballance cracks open the dense PMBOK tome and attacks it with a rainbow of highlighters. She has color-coded tabs marking risk registers, critical paths, and earned-value equations. She is chasing her PMP certification while I take our two young boys on backyard adventures and keep the dog from stealing page flags.

Watching her diagram work-breakdown structures reminds me that the most reliable habits in software look a lot like the ones we have leaned on while we were flipping houses during the pandemic (we were bored and feeling ambitious), running weekend projects with the children, or building a lava rock rendition of our Surname “Ballance” in the California desert so that it’s visible from space for generations to come as pictured above. You can see it on the live satellite maps at 32.876889426358034, -114.68650579982852 (zoom all the way in).

Our three house-rules:

• Break the work into the smallest slice that still delivers value

• Finish that slice before chasing the next shiny thing

• Inspect what we built, learn, adjust, and repeat

Call it iterative delivery, call it common sense, call it anything but the buzzwords I’ve conveniently not mentioned anywhere in this article. The label never matters as much as the mindset, and some of them come with way too much drama lately.

After more than twenty years alternating between IC trenches and engineering leadership, these are the nine habits I scribbled on one of Kate’s sticky notes this morning. They have steered every codebase, home renovation, and desert art installation we’ve tackled:

1. Shared understanding – everyone should explain why the work matters, not just what it is. Artifacts and ceremonies are just vessels to facilitate clarity.

2. Open dialogue – Encourage the team to bring questions and concerns to the surface early, not just wait for the retro.

3. Collective ownership – a broken build or a crooked cabinet belongs to all of us until it is fixed.

4. Trust in handoffs – you can step away without fear the project will stall.

5. Cross-functional planning – Involve design, test, stakeholders and engineering early in the process. Poke holes in the plan from different perspectives.

6. Graceful adaptation – Fresh data points should pivot the plan without drama. Respond to the data and adapt accordingly.

7. Playbook mindset – every issue becomes a lesson that prevents the next one. Folks who have worked with me are probably sick to death of me talking about blameless postmortems, but I’m a firm believer in their value.

8. Boots on the ground – the people closest to the work decides when it is “done done.”

9. Quiet recognition – celebrate the invisible refactors as loudly as the feature launch.

If your team is light on any of these, start small: deliver one thin slice of value, see how it feels, then iterate. Your PagerDuty shift will stay quieter, launches calmer, and the crew will still have energy to cheer the next win.