About

Hi, I'm Jamie.

I started out studying web design, drifted into writing code, and spent the better part of two decades in agencies building websites and apps for brands you've probably stood in a queue for. Somewhere along the way I became the developer who didn't mind answering the work phone. A bit of client comms here, a bit of timeline wrangling there. Nobody called it project management. It was just "someone should probably deal with this", and that someone kept being me.

Eventually the transition made itself official. The first project I managed without writing a single line of code was worth over £250k, and I kept waiting for the urge to open VS Code and just do it myself. It never came. The developer brain didn't switch off, though. It just started paying attention to different things: dependencies, risks, the conversation between a designer and a developer that's going to become a problem in three weeks if nobody steps in.

That's what this blog is about. Project management from someone who's sat on both sides of the ticket. The unglamorous mechanics of delivery, what a technical background actually buys you in this job, where AI is quietly rewriting the role, and the occasional detour into design, development, or whatever I'm building on the side.

Why "Scope Creep"? It's the PM term for a project quietly growing beyond its original brief. Which is also a fairly honest description of my career. And, if I'm being realistic, this blog.

Jamie's disclaimer: everything here is opinion formed from experience, not gospel. Confidence levels vary by post and I'll usually tell you which is which.