The short version: If you have ever planned a wedding, launched a product with three suppliers who all hated each other, or kept a house move on track with a spreadsheet, you have project management experience whether anyone gave you the title or not. The skills are the same, only the label is missing, and once you learn to name it you can put it straight on a CV or use it to charge more for the work you already do.
The gap between what you did and what you called it
I spent years running events, campaigns, and product launches without once writing “project manager” on a form. I was the “marketing lead” or the “social media person” or, on my worst days, “the one who sorts it out.” It took me an embarrassingly long time to realise that sorting it out, on a deadline, with a budget, and with people who didn’t report to me, is project management. Not adjacent to it. Not “a bit like it.” It.
This isn’t a motivational trick to make you feel better about your CV. It’s a genuine blind spot that costs people money and job titles. I’ve sat across from clients who run six-figure operations from a kitchen table and still describe themselves as “just doing bits of everything.” That phrase, “bits of everything,” is almost always project management wearing a disguise.
What project management looks like day to day
Strip away the certifications and the Gantt chart software and project management comes down to five repeatable things: defining what “done” looks like, working out who needs to do what, tracking whether it’s happening, sorting out what goes wrong, and reporting on it to someone who wasn’t in the room. That’s the whole job. I go into this in what project management is about, because most explanations make it sound far more abstract than it is.
Here’s where people miss it. You don’t need a Jira board to have done all five of those things. You need a plan, a way of tracking it, and the nerve to chase people. That’s it.
A real example: the office move nobody called a project
A few years back I helped a small marketing agency, twelve people, move offices in Reading over a bank holiday weekend. The person who ran it, Sarah, was the office manager. Not a project manager. Not on the org chart as anyone senior. But look at what she did over six weeks:
- Built a timeline working back from the Tuesday morning deadline, with four checkpoints
- Coordinated three external suppliers (removals, IT, cleaners) who had never worked together and didn’t know each other’s schedules
- Managed a budget of just under £14,000 and flagged a £900 overspend on the IT cabling two weeks before it happened, not after
- Ran a risk list on a whiteboard: what happens if the removals van is late, what happens if the internet isn’t live by Monday
- Reported progress to the managing partner every Friday in four bullet points
That is a textbook project, delivered on time, on budget, with stakeholder management, risk tracking, and a communication plan. Sarah called it “sorting the move.” When I told her she’d just run a proper project, she laughed and said she’d never put it on her CV because it “wasn’t really her job.” It absolutely was her job. She just hadn’t been given the vocabulary to describe it.
Where this experience is hiding in your own work
Look for these patterns. They’re the ones I see most often in people who insist they have “no experience” in this area.
- Event or wedding planning: budget, vendor management, timeline, contingency plans, a deadline that cannot move. That’s scope, cost, schedule, and risk, the four things every PMP exam question is really asking about.
- Running social media for a small business: content calendars, campaign deadlines, coordinating a designer and a copywriter who never talk to each other, reporting results to a client monthly. If you’ve ever worked out what to charge for social media management, you’ve already priced project work, you just called it a retainer.
- Parenting logistics: three kids, two schools, a football match, a dentist appointment, and a broken washing machine all in one week, resourced and sequenced without a single missed slot. Nobody puts this on a CV and it is harder resource planning than most junior PM roles.
- Side hustles and freelance work: taking on a client project, scoping it, delivering it, invoicing it, chasing the late payment. Full project lifecycle, start to finish, on your own.
- House renovations: managing a builder, an electrician, and a plasterer who all blame each other for delays, on a fixed budget, with a moving deadline because your in-laws are visiting in October.
If you’ve done two or three of these, you have more real project experience than plenty of people with “Project Coordinator” on their LinkedIn who have only ever updated other people’s spreadsheets.
The uncomfortable bit nobody tells you
Here’s what most articles on this topic won’t say plainly: having the experience is only half the battle, and sometimes less than half. Hiring managers and certification bodies don’t care what you did, they care what you can prove and describe using their language. I’ve watched skilled people get rejected for PM roles not because they lacked the skill but because they described running a £50,000 event launch as “helping out with an event,” while someone with objectively thinner experience described a small internal process tweak as “leading a cross-functional initiative to improve operational efficiency.” The second person got the interview. That’s not fair, and it’s not really about merit at that stage, it’s about translation. If you want to know exactly how much of this real-world experience counts toward something formal like the PMP, it’s worth reading how much project management experience you need before going for PMP, because the answer is more generous than people assume, and includes non-job-titled work like Sarah’s office move.
The other uncomfortable truth: not every messy juggling act counts. Managing your own to-do list is not project management. Coordinating one other person for one afternoon is not project management. The line is whether there was a defined outcome, a deadline that mattered to someone else, a budget or resource constraint, and at least one point where things could have gone wrong and you had to actively manage that risk rather than just hope. If none of those existed, be honest with yourself, it’s admin, not a project. Overclaiming here backfires just as badly as underclaiming, because an interviewer will ask a follow-up question and the gap will show immediately.
How to turn this into something you can use
Recognising the experience is step one. Making it useful is a separate job, and it takes about an hour if you do it.
- List every project-shaped thing from the last five years. Work, volunteering, home life, side projects. Aim for at least eight to ten entries, don’t filter yet.
- For each one, write down the four things that matter: what was the deliverable, what was the budget or resource limit, who were the stakeholders you had to keep happy or informed, and what went wrong that you had to fix.
- Attach a number wherever you can. Not “managed a small budget” but “managed a £14,000 budget across three suppliers.” Not “coordinated a team” but “coordinated a five-person team across two time zones.”
- Cut anything that fails the test above. No deadline that mattered, no constraint, no risk managed, no stakeholder to report to, it’s not a project, leave it off.
- Decide whether you want to formalise it. If three or more of your entries meet the hours threshold, look at where to get a project management certification and which one is worth paying for, because some of the cheaper ones aren’t recognised by the employers who’d care.
I did this exercise myself when I was rebuilding my consulting business a few years ago, after five hard years where I had to relearn how to describe my own work. I found I’d run something close to forty separate “projects”, product launches, event series, client campaigns, that I’d never once framed that way. Writing them down changed how I priced my own consulting work, because I stopped underselling coordination as an afterthought and started charging for it as the actual skill it is.
What this means if you’re changing careers
This matters most if you’re trying to move into a new field and think you’re starting from zero. You’re rarely starting from zero. The same logic that applies to spotting hidden project management experience applies to other career pivots too. Someone moving into a remote frontend developer role without prior remote experience still has real transferable proof points, they just need to find them and name them the way the industry expects. It’s the same muscle: stop describing your work in your own private language and start describing it in the language the room you want to enter uses.
And if social media is your route in, the same rule applies there too. If you’re building from nothing, start by looking at where to learn social media management from scratch, because campaign work in that field is project work with a different name on the door, and every client project you deliver adds to the same pile of experience you’ll one day need to describe on a CV or a rate card.
The quiet cost of not naming it
The real cost of not recognising this isn’t a missed job title, it’s underpricing. People who don’t see themselves as project managers routinely charge for the “doing” and give away the “managing” for free. Sarah, from the office move, wasn’t paid a penny extra for running that project, it was folded into her existing office manager salary. A freelance social media manager who’s coordinating four suppliers, a content calendar, and a client’s nervous energy every month is running a project, not just posting content, and should be pricing accordingly. Once you can name the skill, you can put a number on it. That’s the whole point of doing this exercise honestly rather than as a feel-good CV filler.
Frequently asked questions
What counts as real project management experience if I’ve never had the job title?
Anything with a defined deliverable, a deadline that mattered to someone else, a budget or resource limit, and at least one risk you actively managed rather than just hoped would resolve itself. Events, house moves, client campaigns, and even complex family logistics can qualify if those four elements are present.
Can this unofficial experience count toward a PMP or other certification?
Often yes, most certification bodies count hours of documented project leadership regardless of your job title, provided you can describe the scope, timeline, and outcomes clearly. Check the specific hours threshold before assuming, because the requirements vary between certifications.
How do I describe this experience on a CV without sounding like I’m overclaiming?
Use specific numbers instead of vague verbs: a budget figure, a team size, a deadline, a measurable result. “Coordinated a £14,000 office relocation across three suppliers with zero missed deadline” reads as fact, not spin, because it’s specific enough to be checked.
Is managing my own to-do list or a single afternoon of coordination enough to count?
No. That’s admin, not project management. The difference is whether there was genuine complexity, other people depending on the outcome, and a real constraint you had to manage, not just a list you personally ticked off.
