Hi everyone!

I think my brain is starting to shut down for 2024. This issue is simply three disconnected things that came to mind, including:

1. A tale recounting my recent brush with professional indignation

2. Engineering good outcomes: An ingredient list

3. A small favour to ask!

Professional indignation!

There's a special kind of sting associated with being professionally insulted. 

It's the hot flush of anger, but with this cold and analytical centre. Unlike the indignation you might feel when your partner fails to load the dishwasher correctly, with professional insult your anger is justified, rational, and founded in your professional experience and knowledge.

You know when you encounter work or standards that fall drastically short of what you know to be the proper, competent level of quality for your field. You aren't defending dishwasher stack order, no, you are defending your profession!

It's weirdly emboldening.

This is how I felt about the IIBA state of business analysis survey. Which is unfortunately no longer live so if you missed it, you can't personally experience the terribleness. But, lawdy, what an absolute disgrace of a survey. 🤦‍♀️😭💩

It is so deeply frustrating to see something that could be super helpful to the community be wasted for the purpose of manufacturing data to sell more certifications. If you're a member of the IIBA, you should be insulted. 

Gosh, I'm not a member and I'm insulted!

First came anger, then frustration, then indignation. 

Then I had the bright idea to do my own state of analysis survey. I even got as far as buying a domain name, creating a beta survey, start user testing, and engaging with potential supporters/promotors. Turns out anger is an extremely powerful motivator for me! 😅

I'm happy to report that my survey ambitions have ebbed along with my frustration on the topic. I'm still working on it, but expect something more pulse-check-ish than something overly comprehensive to come in 2025!

Engineering good outcomes requires …

It is incredible to me that you can be struggling with a concept for ages – sometimes years – and just one single conversation can crystallise the previously vaporous thoughts into something tangible.

That's what happened to me last week. I was participating in some chap's university research on all the "X driven" approaches to development (ATDD, TDD, and BDD) and the process of being forced to articulate my views in relation to those methodologies made some key threads clear.

Once I had the thread I could pull it, work on it, refine it.

The result?

A better answer to the question of "how to get stuff done" than I've ever articulated before. And the answer is five things that guide my approach to, well, everything.

Good outcomes happen when you:

1. ⛲️ Don't push, pull: Let demand set the pace; avoid overloading the system.

2. 🖼️ Think big, move small: Understand the context; take manageable steps.

3. 📐 Right-size the rigour: Add process and governance in proportion to the risk and the stakes.

4. 🐛 Dig until done: Pursue details when they're needed and not before.

5. 👀 Mind the humans: People complicate everything; be caring (but also wary)

Obviously there is more thinking and tidying to do, but it feels like an exciting direction, full of future articles, discussions, and interesting things to dig into! So be warned, 2025 is looking very outcomes engineering focused! 

A favour to ask

I've been doing a lot of planning and looking ahead to 2025 and you can help! I'd love you to just click reply on this email and let me know:

• What's one thing you especially liked from me this year?

• What's one thing you think I should change?

• What's one thing you'd like to see me do next year?

I cannot tell you how helpful it would be to hear from 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