LECTURESFoundational Thinking10

Supplementary course

Bird's-Eye Thinking

Exhaust the combinations of conditions

A "thinking method that exhausts the combinations of conditions," usable in every setting — operational design, system design, decision-making. Internalize the template with three worked examples (operations / CRUD / status transitions).

Bird's-Eye Thinking

─ ARTICLE COVER

Foundational ThinkingSupplementary course

§I ─ POSITION

Where this course fits

A supplementary course of the DX-project curriculum. A shared skill for discovering gaps in every setting across Ph.1 to Ph.6.

§II ─ TAKEAWAYS

What you will learn

  1. 01

    Exhaust by expanding conditions into an "axis × axis" matrix

  2. 02

    Use it appropriately across the three example-based patterns of operations / CRUD / status

  3. 03

    Reduce the after-the-fact regret of "I should have noticed if I'd thought about it"

§III ─ EXCERPT

Excerpt from the course

01

Why bird's-eye thinking

Gaps in requirements definition, overlooked boundaries in business workflows — 70% of these come down to whether you hold a "template of how to think." Bird's-eye thinking builds the habit of setting up axes and fully enumerating the combinations.

02

The 3 typical patterns

The three patterns that recur most in practice. Keep these as "templates."

  • Operations matrix — department × operation / phase × role
  • CRUD table — screen × operation (Create/Read/Update/Delete) × role
  • Status transition table — state × event / state × operable-or-not

03

How to choose the axes

Choose the wrong axes and the matrix dies. Pick from one of "an axis where the targets increase or decrease," "an axis that branches by condition," or "an axis that changes over time." Example: for CRUD, "role (increase/decrease) × operation (branch)"; for status transitions, "state (time) × event (branch)."

04

How to fill the cells

Try to fill every cell and you'll give up. At first, fill them coarsely on three levels: "○ / ✗ / unclear." The "unclear" cells become the points for additional discovery or analysis. Perfectionism aimed at producing a "sense of having done it" in requirements definition is the enemy.

05

The gap between the "focus of the discussion" and "all patterns"

The root cause of gaps is seeing only "the one cell currently being discussed." For example, in a meeting where you're talking "for small and mid-sized firms…," "what about large firms?" gets dropped later. The problem is not defining, before the discussion, "what combination of axes is this about?"

New inquiryExisting inquiryComplaint
Large firms???
Mid-sized firms???
Small firms← talking about now??

06

Trigger condition: when 2 or more axes are found

There's a right time to use bird's-eye thinking. Always making a table is a waste. It triggers when the following three conditions are met.

  • ① There's an objective you want to achieve (design / decision / organization)
  • ② You're trying to decompose the target for that objective
  • ③ Two or more decomposition lenses (axes) have been found ← here's where bird's-eye thinking comes in
─── Continue in the download edition ───

§∞ ─ DOWNLOAD

Get the full materials, exercises and answers
in the download edition.

─ EXERCISE

A worksheet plus 6 exercises and a test. Through real examples, internalize "how to choose the axes" and "how to fill the combinations."

Lecture slides

Every slide of the course

Cheat sheet

Quick reference for the field

Exercises

With answers and grading

Advanced / test

Hands-on plus rubric

INCLUDED PDFS ─ 7files

IT Consulting Guidebook | A Systematic IT Consulting Method Across 18 Lessons, from IR Analysis to PM | IPLoT Inc.