- Jimmy Briefs
- Posts
- #35 The consequences of making up your job title
#35 The consequences of making up your job title
It brings a whole new meaning to the question: "so what do you do?"
Hi everyone!
It has been 2.5 months since I officially became an outcomes engineer. Isn't it appropriate to do 2.5 learnings then? But first ...
I need your help! I'm working on a podcast idea and I'm collecting (real) messy problems! If you have an issue related to business, product, delivery, analysis, or something vaguely related to getting stuff done – I'd love to hear about it!👇
And with that out of the way … the learnings!
1. I've had to explain myself a lot
I’ve even got the spiel down now:
"I'm Hannah, I'm an Outcomes Engineer – my background is in project, product, digital, and delivery. Most of my background is in business analysis – the-get-stuff done kind of business analysis"
(That last part often gets a wee chuckle).
The problem with a made-up role is also what is so good about it: you're not getting boxed into predefined expectations, but that means you're also constantly in sales mode. Nothing is a given. Every other day, I'm suggesting approaches, offering to help, and proposing ways to keep things moving. More than once I've found myself looking at all the people on the call, trying to work out who should own that action, and realising that – oh! – I could own that action! It could be me! 🙋♀️
At first, I tried to grab everything (because I'm greedy), but I'm realising that unless I want Outcomes Engineering to be just a new name for a Senior BA role, then I need to be super deliberate about positioning my contributions.
So that's what I've been doing.
It has made me confront how little I've thought about this up until now. Previously, I've just done all the things that were expected of the role without discretion. Which is sort of insane when you think about it.
The takeaway: we all – yes, you included – should be asking ourselves: "Does this move me towards the professional I want to be? Or just maintain the status quo?"
2. Network, Network, Net worth!
My role reports to the Head of Delivery. That means I'm not in the BA club, neither am I in the product club. Technically, I'm not even in a specific delivery team, but work across multiple. I'm an aberration.
I'm expected (and want) to go to where the fires are biggest. I get deployed on missions or to support an existing mission. There's no clear home base. It's super freaking fun!
But here's the part I hadn't realised before I was in it: ALL my work is subject to consent from the people I'm working with. My authority and legitimacy is entirely derived from the cooperation of the rest of the team. I don't have a traditional role and remit to lean on.
It is all dependent on influence, social credit, politics, and network. All. Of. It.
Now I generally would have claimed that I'm pretty good at working out the network and politics of a workplace, but this role has required much more of that than I ever thought possible. It is less that the network and my relationships help me to be better at my job, and more that my new squishy role is entirely dependent on it.
The default is to not have me involved. And that will stay the default, unless I am able to convince someone – or often many someones – otherwise. Flow not force has taken on a whole new meaning in this context.
I've realised that I've previously seen the network as an add-on. I'm learning that it is a foundational piece of the puzzle. Again, something I could have leveraged earlier had I realised it – so please learn from my oversight!
The takeaway: Map out your network and stakeholders, not just for your project or change programme, but to build your understanding of how things work in your workplace so you can more effectively influence the happenings. I'm not joking – start by listing the closest five decision makers in your part of the org, and map out who influences them ... and go from there.
2.5 I had no idea what I was getting myself into
Yep. None. I'm flying by the seat of my pants, and it is both excellent and one of the most stressful things I've done.
I've had to keep reminding myself that new stuff is always stressful and that growth happens in discomfort.
What are you doing that scares you?
As always, I would love to hear your thoughts on this (or anything else), so do reply to this email, DM me on LinkedIn, or send me a letter via pigeon.
I cannot tell you how much I like hearing from y'all!
And until next time, stay excellent! 💖
Hannah
