Use your pattern as a filter. Use evidence as the gate.
A repeatable framework for framing, filtering, stress-testing, finalising, and reviewing decisions—using the Day Pillar as an optional reflective hypothesis rather than a command.
Separate the person, the process, and the evidence.
Decisions may stall because the question is vague, authority is unclear, criteria conflict, information is missing, stakeholders disagree, risk is unbounded, or the decision-maker is tired, threatened, or overloaded.
A Day Pillar interpretation may add a reflective question about pace, trust, pressure, or communication. It should not become a fixed claim about “wiring,” nor override data, consent, expertise, duty, or consequence.
The protocol below works without BaZi. If you include the Day Pillar, place it inside the Filter stage and compare the hypothesis with observed behaviour.
Move from ambiguity to accountable action.
Each stage produces a written output. If a stage cannot be completed, pause rather than forcing certainty.
Frame
Define what is actually being decided.
- Decision and owner
- Deadline and reversibility
- Alternatives, including delay
- Success and veto criteria
Filter
Apply reality, ethics, and optional personal lenses.
- Evidence and constraints
- Values and obligations
- Capacity and stakeholder effects
- Day-Pillar hypothesis, if useful
Forecast
Stress-test each surviving option.
- Pre-mortem and downside
- Second-order effects
- Base, upside, and failure cases
- Mitigation and exit rules
Finalise
Convert the choice into execution.
- Decision in one sentence
- Owner and first milestone
- Communication sequence
- Review and pivot date
Use questions—not archetype assignments.
Your exact pillar may prompt reflection, but the answers must come from current behaviour and context.
What do I protect first?
Capital, safety, speed, quality, harmony, autonomy, reputation, or opportunity?
Check: Is that priority appropriate to this decision?What earns commitment?
Evidence, consistency, expertise, transparency, loyalty, process, or shared momentum?
Check: What proof would change my mind?What tempo improves quality?
Immediate triage, one night, staged testing, consultation, or a fixed review cycle?
Check: Is delay gathering information or avoiding responsibility?How should the case be presented?
Data, narrative, process, options, consequences, visuals, or direct recommendation?
Check: What does the receiver need—not only what do I prefer?What distorts my judgment?
Fatigue, urgency, status threat, ambiguity, conflict, isolation, or social pressure?
Check: Which guardrail reduces error?How do I recover from a miss?
Facts, space, conversation, apology, plan, restitution, or rapid iteration?
Check: What does the affected party require?Urgent decisions and complex decisions need different clocks.
For urgent, reversible action
- Confirm immediate safety and legal constraints.
- Name the decision owner and the smallest reversible step.
- Cap exposure in time, money, access, or reputation.
- Identify the next information checkpoint.
- Act, document, and escalate if the threshold is crossed.
For consequential, time-bounded choices
- Hours 0–3: frame the question, owner, criteria, and vetoes.
- Hours 3–8: gather decision-critical evidence and missing expertise.
- Hours 8–14: build baseline, bold, and buffered options.
- Hours 14–20: pre-mortem, consult, test assumptions, and rest if possible.
- Hours 20–24: decide, assign, communicate, and set the review trigger.
Review the process—not only the outcome.
A good outcome can follow a weak process, and a sound process can still meet bad luck. Track both decision quality and result.
Pause when judgment is compromised or authority is missing.
A protocol cannot legitimise an unsafe, unlawful, coercive, discriminatory, or professionally unsupported decision.