Latest / Career Coaching with Fexingo: Professional Coaches, Career Counselors, and Guidance for Workers / How a Career Pain Point Audit Reveals Your Next Move
Transcript
- Lucas: So, we talk a lot on this show about things like career values audits and skill portfolios — forward-looking tools that help you figure out what you want next. Luna: Right, all about building toward something. Lucas: Exactly. But sometimes the clearest signal about what you should do next comes from looking backward — specifically, at what has consistently frustrated you across jobs. I've been calling it a Career Pain Point Audit. Luna: Pain point audit — I like that. So instead of asking 'what do I want?', you're asking 'what keeps hurting?'. Lucas: That's the gist. And I want to walk through a real example because the exercise is simple but the results can be surprisingly specific. A friend of mine — let's call her Rachel — had been a marketing manager at three different companies over about eight years. Each time she left, she told herself it was the industry, or the boss, or the commute. Luna: Classic attribution error — blame the situation, not the pattern. Lucas: Exactly. So I had her do this audit. Step one: list every role she'd held for at least six months, and beside each one, write down three to five recurring frustrations from that job — not one-off annoyances, but things that bugged her week after week. Luna: And what came up? Lucas: At her first job, she wrote: 'constant scope creep on campaigns', 'never enough time for strategy because of execution demands', and 'felt siloed from product team'. Second job: 'too many last-minute requests from leadership', 'strategy meetings that never turned into action', 'no visibility into product roadmap'. Third job: 'endless ad hoc reporting requests', 'my team kept getting pulled into fire drills', and 'marketing treated as a service desk, not a strategic partner'. Luna: Oh, look at that — there's a theme. Across all three jobs, she's frustrated by being reactive, not strategic, and by not having a seat at the table early enough. Lucas: That's step two: code the pain points into themes. Rachel's themes were: lack of strategic influence, reactive work culture, and poor cross-functional integration. Three themes, all consistent across eight years and three employers. Luna: And then step three — what do you do with those themes? Lucas: You design a filter for your next move. Rachel stopped looking at job titles and started looking at the actual operating model. She took a role at a mid-size B2B company where marketing sits on the product council, there's a formal quarterly planning cycle, and the team has a policy of no ad hoc requests — everything goes through a weekly triage. She's been there eighteen months and says it's the first time she hasn't felt that low-grade dread on Sunday night. Luna: That's huge. And it's so much more actionable than 'I want a job with more meaning' or 'I want better work-life balance'. Those are too vague. Lucas: Right. The pain points give you specific, observable criteria. 'No ad hoc requests' — you can ask about that in an interview. 'Marketing sits on product council' — you can look for that on an org chart or ask in a meeting. It's a decision tool, not a wish list. Luna: So practically, how does a listener do this today? Like, what's the minimum viable version of the audit? Lucas: Take thirty minutes. Open a document or get a notebook. List every job you've had for at least six months. Under each, write down three to five recurring frustrations — be honest, not diplomatic. Then look across the list and group them into three to five themes. That's it. Luna: And what if someone finds that their pain points are all about one thing — like micromanagement? Lucas: Then that becomes the single most important filter for your next move. You might want to target organizations that have a track record of autonomy — maybe companies with flat hierarchies, remote-first cultures, or roles that are measured on output rather than hours. But here's the thing — the audit also helps you see when a pain point isn't about the job but about the industry or the career path itself. Luna: Give me an example. Lucas: I had another friend, a software engineer, who did the audit and found that his top recurring frustration across three roles was 'never getting to see the impact of my work'. He was writing backend infrastructure — important stuff — but his users were other engineers, not end customers. So his pain point wasn't about his employer, it was about the type of engineering. He moved to a product-facing frontend role and the frustration vanished. Luna: So the audit can also tell you when you're in the wrong function, not just the wrong company. Lucas: Exactly. And that's a much bigger insight. It's the difference between rearranging deck chairs and switching ships entirely. Luna: One thing I want to flag — a lot of people might feel like cataloging their frustrations is just complaining. How do you frame it so it feels productive? Lucas: I think the key is to treat it with the same clinical detachment you'd use if you were a consultant diagnosing a business process. This isn't 'what annoys me' — it's 'what consistently produces friction in my work system'. You're not blaming anyone, you're identifying friction points. And the goal isn't to vent, it's to extract a signal that helps you build a better fit. Luna: I like that reframing. So it's not a complaint list — it's a diagnostic. Lucas: Right. And I'd say one more thing. If you do this audit and you find that your pain points are all about things you can't change — like you hate ambiguity and you work in a startup, or you hate repetition and you're in compliance — then the audit is telling you something fundamental about the kind of environment you need. Luna: And that honesty can be uncomfortable but it's also liberating. Because you stop trying to force yourself to like something you'll never like. Lucas: Exactly. And look — if this episode helped you think about your own career patterns in a clearer way, that's the whole point. If it was worth the cost of a coffee to you, we'd love it if you'd support the show at buy me a coffee dot com slash fexingo. It's what keeps the podcast ad-free and lets us keep doing deep dives like this. Luna: Yeah, every little bit helps us keep the lights on and the coffee brewing. Seriously, thank you to anyone who's already supported. Lucas: So back to the audit — I want to offer one more refinement. After you identify your themes, rank them by how much they matter to your daily experience. Not all pain points are equally important. Luna: Right, because maybe you can tolerate a little bit of reactive work if you have high autonomy, but you absolutely cannot tolerate a micromanager. Lucas: Exactly. So rank them from most to least deal-breaking. Then when you look at your next opportunity, you don't just check whether it avoids your pain points — you check whether it avoids your top two or three. Everything else is negotiable. Luna: That's a really practical filter. I'm going to do this myself this weekend. Lucas: Let me know what you find. Sometimes the pattern is so obvious in hindsight that you can't believe you missed it. Luna: I will. And for listeners — if you try the audit, we'd love to hear what themes surfaced for you. Lucas: That's it for this episode. See you next time.