• Late this week Bryan Finster dropped a powerful article “5-Minute DevOps: The Three Wrongs”. I like how Bryan accurately explains concepts around value hypothesis and experimentation (similar concepts that I tried to deconstruct in Effort, Impact and Experimentation in Testing - and it is very likely that I will borrow some quotes) and common pitfalls:
    • “One of the biggest hurdles to delivering something valuable is assuming the idea is valuable. Instead, we should treat the idea as a value hypothesis.”
    • “The idea of “we’ll deliver this and be done” is simply a fantasy, and any plan based on that assumption fails before it begins.” - No more words needed. A. Must. Read.
  • Continuing with the topic of experimentation - I like the saying “Good tester thinks like a scientist.” Danyel Fisher spotted exactly that in his article “Measure, Design, Try: On Building New Things” explaining and illustrating how similar cycles are applied in both Academic and User Researches.

  • Earlier this week Simon Sinek’s The Optimism Company posted an interesting article focused on Truly Meaningful Work. It does not only write about purpose, “purpose-washing”, but also suggest 5 green flags (and I probably see that as a nice tool to challenge your own “North Star”):
    • “Your company actually puts resources into supporting the purpose.” - Remember The one with Chaos and its 3 Antidotes (clarity, consistency, support)? So, this is support.
    • “The purpose is actively communicated to everyone in the organization, not just a select few.” - This is clarity.
    • “The company provides data that demonstrates tangible impact related to the purpose.” - Data, impact, purpose and a proper emphasis. Data creates clarity, demonstrates facts, justify efforts.
    • “The purpose isn’t solely focused on generating revenue.” - Based on my personal experience in consultancy business, this one sounds like the most difficult one because of many reasons.
      For example… When one is working in an engagement as a consultant providing some service, and gets paid based on spent hours (effort), and for some time they feel stuck and not providing real value (impact), but their client does not spot that as the client is “hypnotized” with the effort - should the consultant voice that “feeling of no impact/progress” to their client and put the engagement at risk? What will the client do with such information? Will the client thank the consultant and say “goodbye”? Or will the client actually recognize the honesty and fairness, will they help to find more value opportunities, and navigate the consultant’s efforts towards impact (and better end-product)? Should the consultant care not only about their revenue, but also about the client’s revenue, and client’s product’s purpose (to be focused not solely on revenue)? Those are good questions. Ethics, sustainability, trust, and some other friends enter the room…

    • “It evolves and adapts based on key performance indicators (KPIs) and rewards.” - I am not sure I understand this one. For me, it conflicts with consistency/stability. Talking about high-level purpose, company vision/mission and similar things, I don’t see that changing often. That would bring back the Chaos. (UPDATE: as I have guessed, Simon Sinek’s team have got lost in translation as the idea in the original article goes as “Processes, structures and careers evolves and adapts based on purpose.” That makes sense.)
  • Have you ever doubted yourself or your vision, your own ideas? Have you ever captured how your motivation changes when you present your idea, prototype or draft for discussion, and you get those “yes, but what if…” responses? Gergely Orosz, the author behind his very recent bestseller “The Software Engineer’s Guidebook”, shares a powerful story of how one should stick to their idea if they truly believe it. And if you still don’t have a Christmas present for that one smart friend working with computers and other smart people, take it as a hint.

  • Probably, it was impossible to miss the news about OpenAI board firing Sam Altman. In my opinion, it is impossible to know what will happen next, we can only speculate, so let’s not do that. Instead, I wanted to highlight an amazing demo, and to be more exact, it was a quite recent OpenAI DevDay Opening Keynote with Sam Altman in front of it. Not sure if we can put that keynote on the same shelf with Steve Jobs and his demos of iPad or iPhone, but Sam Altman is getting close to it. A lot of stories focuses on impact and that simply captivates.