@rapidsystemshub In my experience people just instinctively think in terms of solutions and outputs. The underlying problems and outcomes are often hard to express clearly, and most stakeholders are facing the kind of time pressure that makes expanding on the problem unappealing.
It feels ridiculous to write this sentence, but: Solutions that don’t solve the problem ultimately lead to failure.
So maybe stop presenting work you don’t believe in? Here are 4 steps to avoid this common pitfall.
🧵👇
@rapidsystemshub “Can you help me understand the problem we’re trying to address here?”
That would be my very first move. At the very least that opens the door to suggestions on how to be be more problem oriented.
If you enjoyed this:
• Like or reply to this tweet with your thoughts!
• Follow me @chrilson for more frameworks on making room for good work to happen
To recap:
1️⃣ Run the scenarios
2️⃣ Pros & cons of each
3️⃣ Have a preference
4️⃣ Take your time
✨ Forgive yourself
👆This’ll be my post-it note, stuck to my monitor.
@rapidsystemshub Happened to me too last week 😕 I’ve switched to writing in a text editor until the content is ready, then copy-pasting to Typeshare for formatting and posting.
@MartineGuernsey Thank YOU for the feedback and words of encouragement, Martine! I’m a systems thinker too, and can easily feel off-balance when circumstances don’t cooperate. Almost feels like an opportunity to devise a process for when other processes don’t work out 😉
@rapidsystemshub Since I know for a fact you’re not a dummy lol, I’m going to treat this as an important bit of feedback: I need to keep working on shortening and simplifying!
Thanks Vasily 🤜🤛