PDCA on serotonin
Skeletal formula of serotonin, C10H12N2O. Structure originally drawn in ChemBioDraw Ultra 12.0 by Ben Mills

PDCA on serotonin

I’ve been reflecting on the structural differences between the PDCA cycle and the OODA loop. One thing that stood out is that OODA has a single point of intervention-Act-while PDCA has two: Do and Act. My assumption is that PDCA is designed for situations with periods of relative stability between interventions, which is why it makes sense to formalize both “Do” and “Act” as distinct steps. In contrast, OODA is built for environments in constant flux, where it’s all about continuous action and rapid adaptation.

With a bit of creativity, you could even say that PDCA contains two OODA loops: one within “Do” and another within “Act.”

This simplicity really appealed to me, so I tried to distill the process down to just Study and Act-where “Study” encompasses Observe, Orient, and Decide. However, I soon realized that my interpretation of “Study” assumed that humans are purely rational beings. In reality, decision-making also involves affective, intuitive, and social dimensions.

That realization got me thinking about serotonin, and to a more human interpretation of what it means to thrive-or at least survive:

  • Look - initial gathering of raw data or facts; sensory input
  • See - processing and interpreting what is observed; making meaning
  • Feel - emotional and intuitive response; embodied awareness and resonance
  • Spark- interneving intentionally, based on integrated perception and feeling

 Look - initial gathering of raw data or facts; sensory input

1.      Assess situation: What pain, risk, or opportunity exists?

a.      If acceptable, deprioritize

2.      Determine urgency: How soon must action occur?

a.      If not immediate, schedule for later

3.      Consider collaboration: Do others need to be involved and is there time to involve them?

a.      If yes, bring them in

4.      Evaluate information needs: Are more facts required? Is there time to gather them? Will the situation remain stable?

a.      If yes to all, gather additional facts

See - processing and interpreting what is observed; making meaning

5.      Consider interpretation needs: Is further consideration needed? Is there time? Will the situation remain stable?

a.      If yes to all, interpret the observed information gathered by considering both conscious reasoning and intuitive insights, and integrating feedback and lessons from previous cycles

Feel - emotional and intuitive response; embodied awareness and resonance

6.      Clarify expectations: Is the desired outcome known, or will it emerge through action?

7.      Make decision: Based on available facts, interpretations, intuition, and resources

Spark - interneving intentionally, based on integrated perception and feeling

8.      Spark change: Ignite a response in the system, continually sensing intermediate progress and adapting your approach as the system evolves.

9.      Capture learning: Document outcomes, unexpected challenges, and new variables. Categorize insights as immediate (for current cycle adjustments) or future (for later cycles). Identify patterns to simplify future decisions.

10.  Reassess: Return to step 1 to evaluate progress and determine next steps, incorporating captured learning to update assumptions, priorities, or collaboration needs. Many of the initial steps are quick sanity checks and the sequence is fluid.

The 10-step structure gives it the impression of linearity but it should be interpreted flexibly.

A PDCA expert might say that it lacks structured planning, objective evaluation, and a clear iterative cycle for continuous improvement. An OODA expert might say it blurs observation and orientation, and risks overcomplicating the rapid cycling needed in dynamic situations. Nevertheless, I found it a stimulating reflection.

Joost Vunderink

CTO at Cloud++ | IT Mentor at Blauwmuts Software

5d

I'm not sure I'm following this, but your remark about rational beings reminds me of books like Blink! and Thinking, Fast and Slow. Is that related somehow?

To view or add a comment, sign in

More articles by Mark Smalley

  • Governing value networks

    It's been on my mind for a while, this. In today's interconnected economy, understanding often complex value networks…

    1 Comment
  • XXX

    Here is yet another attempt to unify the various kinds of experience as they appear in different roles in the context…

    14 Comments
  • The Dev-Ops Tariff Treaty

    Given IT Operation’s increasing resentment of Application Development’s perennial PATHETIC AND UNFAIR behaviour, it has…

    6 Comments
  • Goals cascade: strategic alignment for organizational impact

    Introduction: what is a goals cascade and why use it? A goals cascade is a hierarchical framework that translates…

    1 Comment
  • Deep thinking about digital products and services

    Mark Bodman (ServiceNow), Roman Jouravlev (PeopleCert), and I had the pleasure of conducting a two-hour workshop at the…

    1 Comment
  • Beyond analysis: when analysis is not the solution but the problem

    Traditionally, BAs have relied on their analytical expertise to solve problems, define requirements, and deliver…

    1 Comment
  • Why it's hard to market – and how to do better

    Marketing a product or service effectively is a challenge many people face. Too often, the focus is on the offering…

  • Digital philosophical intersectionality

    This is probably my most pretentiously-titled framework yet. Its aim is to help understand digital products and…

    11 Comments
  • Putting a man on the moon

    The story is well-known: In 1962, when President Kennedy visited NASA, he asked a janitor what he was doing. The…

    1 Comment
  • Project health check

    Last year I had occasion to suggest that an organization should reflect on the health of a project. I gave them these…

    5 Comments

Insights from the community

Others also viewed

Explore topics