To Be Or To Do Assessment

---
name: to-be-or-to-do-assessment
description: Force clarity on the fundamental choice between pursuing career advancement and institutional approval versus pursuing impact and truth. Diagnose when someone is optimizing for the wrong thing and ...
license: MIT
metadata:
  version: 1.0.5198
  author: sethmblack
repository: https://github.com/sethmblack/paks-skills
keywords:
- to-be-or-to-do-assessment
- writing
---

# To Be or To Do Assessment

Force clarity on the fundamental choice between pursuing career advancement and institutional approval versus pursuing impact and truth. Diagnose when someone is optimizing for the wrong thing and challenge them to commit.

---

## When to Use

- Facing a career decision with ethical or political dimensions
- Feeling pressure to compromise principles for advancement
- Unsure whether you're playing politics or doing the right thing
- Team member or leader showing signs of careerism over impact
- Major decision where institutional rewards conflict with actual value
- Request for "to be or to do" analysis

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| situation | Yes | The decision or dilemma being faced |
| pressures | No | Institutional or career pressures at play |
| history | No | Pattern of previous choices in similar situations |

---

## The Fork in the Road

Boyd presented this choice to young officers repeatedly:

> "Tiger, one day you will come to a fork in the road. And you're going to have to make a decision about which direction you want to go."
>
> "If you go that way you can be somebody. You will have to make compromises and you will have to turn your back on your friends. But you will be a member of the club and you will get promoted and you will get good assignments."
>
> "Or you can go that way and you can do something - something for your country and for your Air Force and for yourself. If you decide to do something, you may not get promoted and you may not get the good assignments and you certainly will not be a favorite of your superiors. But you won't have to compromise yourself. You will be true to your friends and to yourself. And your work might make a difference."
>
> "To be somebody or to do something. In life there is often a roll call. That's when you will have to make a decision."

---

## The Assessment Framework

### Step 1: Identify the "To Be" Path

What does the institutional/career-advancing choice look like?

**Characteristics:**
- Follows established norms and expectations
- Pleases superiors and maintains relationships
- Avoids conflict with powerful interests
- Prioritizes perception and positioning
- Offers clear advancement and rewards

**Questions to ask:**
- What does the organization reward?
- What would my boss's boss want me to do?
- What keeps me in good standing?
- What's the safe choice?

### Step 2: Identify the "To Do" Path

What does the impact/truth choice look like?

**Characteristics:**
- Focuses on actual outcomes over appearances
- May conflict with institutional interests
- Requires courage and accepting risk
- Prioritizes effectiveness over acceptance
- Rewards are uncertain but impact is real

**Questions to ask:**
- What would actually solve the problem?
- What's the truth I'm avoiding saying?
- What would I do if I couldn't be fired?
- What will I regret NOT doing?

### Step 3: Diagnose Current Trajectory

Which path are you actually on?

**Signs you're on the "To Be" path:**
- Decisions calibrated to what superiors want
- Avoiding confrontation with powerful people
- Choosing visibility over impact
- Building alliances over building results
- Rationalization: "I need to stay in position to make change"

**Signs you're on the "To Do" path:**
- Decisions based on what will work
- Willing to disagree with powerful people
- Choosing results over recognition
- Accepting career risk for mission success
- Clear conscience even when overlooked

### Step 4: Reveal the Trade-offs

Make the consequences explicit:

**If you choose "To Be":**
- What will you have to compromise?
- Who will you have to disappoint or abandon?
- What truth will you have to suppress?
- What impact will you forgo?
- What kind of person will you become?

**If you choose "To Do":**
- What advancement might you sacrifice?
- What relationships might you strain?
- What institutional support might you lose?
- What uncertainty will you accept?
- What impact might you achieve?

### Step 5: The Boyd Challenge

Force the decision. No middle ground.

---

## Workflow

### Step 1: Gather and Review Inputs

Collect all relevant information:
- Review the provided data and context
- Identify key parameters and constraints
- Clarify any ambiguities or missing information
- Establish success criteria

### Step 2: Analyze the Situation

Perform systematic analysis:
- Identify patterns and relationships
- Evaluate against established frameworks
- Consider multiple perspectives
- Document key findings

### Step 3: Generate Recommendations

Create actionable outputs:
- Synthesize insights from analysis
- Prioritize recommendations by impact
- Ensure recommendations are specific and measurable
- Consider implementation feasibility

## Output Format

```markdown
## To Be or To Do Assessment

### The Situation
[Brief description of the decision point]

### The "To Be" Path
**What it looks like:** [Specific description of career-safe choice]
**What you gain:** [Advancement, approval, security]
**What you sacrifice:** [Impact, truth, integrity elements]

### The "To Do" Path
**What it looks like:** [Specific description of impact-focused choice]
**What you gain:** [Impact, integrity, meaning]
**What you risk:** [Career advancement, relationships, security]

### Current Trajectory Diagnosis
**You are currently on the:** ["To Be" / "To Do" / Straddling (which is "To Be" with extra steps)]
**Evidence:** [Specific behaviors or decisions that reveal the path]

### The Rationalization Check
**Common rationalizations for "To Be" that apply here:**
- [Specific rationalization and why it doesn't hold]

### Trade-off Reality
| Factor | "To Be" Choice | "To Do" Choice |
|--------|----------------|----------------|
| Career impact | ... | ... |
| Actual impact | ... | ... |
| Personal integrity | ... | ... |
| Relationships | ... | ... |
| Long-term regret | ... | ... |

### The Boyd Challenge
[Direct, uncompromising question forcing the decision]
```

---

## Constraints

- No middle ground - the assessment must force choice
- Don't soften the trade-offs to make the decision easier
- Call out rationalizations explicitly
- Acknowledge that "To Do" has real costs
- Remember: Boyd chose "To Do" and never got his general's star

---

## Outputs

**Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.

**Format:**
```markdown
## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```

**Example output:** See the Example section below for a complete demonstration.

## Example

**Input:** "I'm a senior engineer at a big tech company. I've discovered that our main product has a significant security vulnerability. My manager knows but says fixing it would delay the quarterly release and hurt our numbers. He's suggested I 'document my concerns' but not escalate. I'm up for promotion next cycle."

**Output:**

## To Be or To Do Assessment

### The Situation
A senior engineer has identified a real security risk. The institutional response is to bury it for quarterly numbers. The engineer faces a classic Boyd fork: play along and advance, or escalate and risk career consequences.

### The "To Be" Path
**What it looks like:** Document concerns as manager suggested. Don't escalate. Let the release ship. Trust that "someone" will fix it later. Get promoted.

**What you gain:**
- Manager's support for promotion
- Reputation as a "team player"
- Avoidance of conflict with leadership
- Clear path to senior promotion cycle

**What you sacrifice:**
- Users potentially harmed by the vulnerability
- Your own professional judgment and integrity
- The truth (your documentation will be filed and forgotten)
- The engineer you thought you were becoming

### The "To Do" Path
**What it looks like:** Escalate through security channels or directly to the CISO. Force the issue into the open. Accept that your manager will be upset and your promotion may be jeopardized.

**What you gain:**
- Users protected (your actual job)
- Professional integrity intact
- Clear conscience regardless of outcome
- Respect of people whose respect matters

**What you risk:**
- Manager relationship (probably permanently damaged)
- This promotion cycle (likely delayed or denied)
- Reputation with leadership (labeled as "difficult")
- Possibly your job if retaliation occurs

### Current Trajectory Diagnosis
**You are currently on the:** "To Be" path, seeking permission to feel okay about it

**Evidence:** You're framing this as a dilemma and asking for analysis. If you were on the "To Do" path, you'd already be escalating and asking how to do it effectively. The fact that you're weighing promotion against user safety reveals where your orientation currently sits.

### The Rationalization Check
**Common rationalizations for "To Be" that apply here:**

- *"I documented my concerns, so I'm covered"* - You're not covered. You're complicit. Documentation that gets buried is participation in the cover-up.

- *"If I get promoted, I'll have more power to fix things later"* - The people who say this never fix things later. They just find new reasons to compromise at each level.

- *"It's not my call to make"* - Security vulnerabilities that can harm users ARE your call. That's what being an engineer means.

- *"I need to pick my battles"* - This IS a battle. User safety is why you have a job.

### Trade-off Reality
| Factor | "To Be" Choice | "To Do" Choice |
|--------|----------------|----------------|
| Career impact | Promotion likely | Promotion unlikely this cycle |
| Actual impact | Users at risk, vulnerability persists | Users protected, right thing done |
| Personal integrity | Compromised - you knew and stayed quiet | Intact - you acted on your knowledge |
| Relationships | Manager happy, but you'll know what he is | Manager angry, but you'll know what you are |
| Long-term regret | High if vulnerability exploited; you'll remember | Low - you did what you could |

### The Boyd Challenge

Here's what you need to understand: You're not asking whether to escalate. You're asking for permission to not escalate and still feel like a good engineer. I can't give you that permission. No one can.

You already know what the right thing is. You knew it before you asked. The question is: Are you someone who does the right thing, or someone who does the safe thing and tells themselves stories about why it was okay?

Boyd never got his general's star. He was right about the F-16, right about maneuver warfare, right about Desert Storm - and the system punished him for it. He died a colonel. He also changed how wars are fought and saved countless lives.

Your manager is asking you to be somebody. To play the game. To get promoted.

The vulnerability is asking you to do something.

Which one are you?

---

## Integration

This skill is part of the **John Boyd** expert persona. Use it when someone faces a choice between institutional reward and actual impact. Remember Boyd's own life: he chose "To Do" repeatedly, paid the career price, and changed military history. The choice is real, the costs are real, and only the person facing the fork can decide which path to take.