Biweeklycast

Biweeklycast

By BiweeklycastBusinessManagement
Download on the App Store

Biweeklycast episodes

  • 56: Spreadsheet mentality

    📺 Watch this episode on YouTube.

    Dima and Slava discuss the spreadsheet mentality and the general difficulties of making data-driven decisions while not loosing the forest for the trees.

    • Theme corner: Dima's season of decoupling


    Spreadsheet mentality (sometimes called "spreadsheet thinking") refers to an overly mechanistic or reductionist approach to decision-making and management that relies too heavily on quantitative metrics while ignoring qualitative factors and nuance.

    • Improving a number while loosing track of why we started this in the first place.
    • Measure = quantify, at least for the purposes of this discussion
    • Cult of data-driven decisions
    • Biweekly 52: Needs Analysis
    • The “Traffic Light” Approach to Problem Solving


    Quotes on the topic

    "What gets measured, gets managed.” – attributed to Peter Drucker or W. Edwards Deming

    "Without data, you're just another person with an opinion." – W. Edwards Deming

    "When a measure becomes a target, it ceases to be a good measure.” – Goodheart’s Law

    “Tell me how you will measure me, and then I will tell you how I will behave. If you measure me in an illogical way, don’t complain about illogical behaviour.” – Eliyahu Goldratt

    55 min
  • 55: Will my next meeting fail?

    📺 Watch this episode on YouTube.

    Dima and Slava discuss all the so familiar ways in which business meetings can fail and share their thoughts on how to prevent meetings from failing.

    • Theme corner: Slava's winter of nucleus and spring of connection
      • Magic of longer vacations


    Meeting is when people get together to achieve a specific purpose


    • Meetings have a goal. Effective meetings achieve their goals.
    • How meetings fail
      • Goal or purpose is not defined
      • Meeting setup is not fit for the goal it tries to achieve
      • People, who are needed, are not in the meeting
      • The purpose of a meeting is misplaced
      • Lack of focus in a meeting
      • Wrong pacing of meeting: too fast or too slow
      • Lack of follow-up
    • Are there kinds of meetings that absolutely must happen face to face? Is it possible to hold any kind of meeting remotely?
    • Is there a best duration for a meeting?
    • The Surprising Secret of Synchronisation
    • Episode about results chain 52: Needs Analysis
    51 min
  • 54: Thought leadership

    📺 Watch this episode on YouTube.

    Dima and Slava discuss the ineffable concept of thought leadership and politely disagree with the author of publication that sparked the discussion.

    • Dima's contribution to the pile of undead documentation
    • The Ineffable Concept of Thought Leadership
    • "Thought leadership is content" – how can that be?
    • Martin Fowler
    • Serhiy Haydaychuk
    • Cortext podcast
    • Meta-discussion: last-minute praparation and different ways approaching multi-step tasks
    46 min
  • 53: Undead documents

    📺 Watchthis episode on YouTube.

    Dima and Slava discuss documentation for systems, processes, and so on, and debate how to prevent it from crossing the line from being helpful to being actively misleading.

    • Dima's January of putting one foot in front of the other
    • Hacker News
    • Fighting undead documentation
    • Documentation evolves independently of the systems/processes it describes
    • Put date of last update in the document to signal that it may be outdated
    • Doing something vs documenting something
    • Finding a updated document can also be a challenge
    • How often and how much to document?
    • Ideally, documentation is integrated into the system is documents
    • 1-2-3 rule for automation writing documentation

    Just feel it!

    55 min
  • 52: Needs Analysis

    📺 Watch this episode on YouTube.

    Dima and Slava kind of follow up on the discussion of Customer Development in the previous episode and talk about chains of results in assessment of customer needs.

    • Other ideas that are connected to what The Four Steps to Epiphany discusses
      • Jobs To Be Done
      • Disruptive innovation
      • Theme corner: Slava's winter of nucleus
      • Results chains in needs assessment: inputs - outcomes - outputs activities inputs
      • "The more "whys" the better."
        • In education, output of a learning activity (e.g. training on giving feedback) is clearly disconnected from desired impact (supportive culture of effective continuous improvement)
        • How does one know if a learning activity is going to lead to the desired impact?
        • How does one know how to do something if they are not an expert in the particular field?
        • Reshaping expectations of a customer
        • 55 min
        • 51: The Four Steps to Epiphany

          📺 Watch this episode on YouTube.

          Dima and Slava read and discuss "The Four Steps to Epiphany" – a classical book for entrepreneurs and startup founders.

          • The Four Steps to the Epiphany: Successful Strategies for Products That Win
          • Steve Blank
          • Opt for paper or e-book. This book isn't really meant to be an audiobook.
          • Key idea: for success enterpreneur needs to hit product-market fit. The book explains how to approach that systematically.
          • Spreadsheet mentality: not everything that is important can be expressed numerically
          • OODA loop: observe, orient, decide, act
          • Thought experiments for CustDev for the theme journal and a coffee shop
          • Jobs To Be Done (JTDB)
          • Ideal Customer Profile (ICP)
          • What if CustDev tells something different from what one wants to hear?
          • 1 hr 7 min
          • 50: More precise

            📺 Watch this episode on YouTube.

            Dima and Slava follow up on the conversation they started in episode 47 and Dima tries to articulate more precisely what he means by people not being specific enough and gives example of common pitfalls of obscure communication.

            • Theme corner: Dima's year of next
            • Example 1: "System X is broken"
            • Clear call to action is very helpful
            • High context and low context situations and personalities
            • Example 2: "Uber for X"
            • Metaphors can be useful, but must not be the only means of describing an idea
            • Effectiveness of metaphors depends a lot on pre-existing context
            • Example 3: "System will to be reliable"
            • Context is important for everything!
            • 56 min
            • 49: Season of strategy

              📺 Watch this episode on YouTube.

              Dima and Slava dive into wonderful season of strategic sessions and try to deduce why everyone does them in December and how to make working on strategy a time well spent.

              • Theme corner: Slava's fall of nucleus
                • Slava's another podcast: Starsphere Talks (in Ukrainian)
                • What is a "strategic session"? And why everyone tries to have them in November and December?
                • Difference between strategizing and yearly planning
                • What to consultants or external facilitators bring to strategic sessions?
                • Leadership and collaboration for strategy development
                • Work on strategy: a point in time or a process
                • What's "strategic" in your work?
                • 56 min
                • 48: Founder Mode

                  📺 Watch this episode on YouTube.

                  Dima and Slava discuss "Founder Mode", an essay by Paul Graham about differences between more founders and hired managers in tech companies.


                  • Founder Mode
                  • Format of an essay
                  • What is special about founders?
                  • Airbnb CEO Brian Chesky: ‘I Never Called it Founder Mode’

                  • "An argument can be perfectly biased in two different ways."


                    • Perils of delegation: where to dive deep and where to step away
                    • Is "manager mode" about driving towards short-term objectives and "founder mode" about executing on a long-term vision?

                    • "Care about what you do."

                      48 min
                    • 47: Can you be more specific?

                      📺 Watch this episode on YouTube.

                      Dima shares his longing for the necessary details and the right level of abstraction, while Slava tries to persuade him that all the details aren't always necessary and everything can be fine anyway.

                      • Dima's knowing-doing gap in working on the theme
                      • Is lack of specificity really a problem and when?
                      • Level of details is what matters, but are all the details always necessary?
                      • Understanding of the details shows even an high level of abstraction
                      • Details vs trust
                      • 1 hr 2 min

                      About Biweeklycast

                      From the publisher's feed

                      Friendly discussions about life, business, engineering, and learning between Dima Malenko and Slava Rudnytskyi.