Mission Engineering 02: Why Weekend vs. Weekday Coffee Requires Separate Scenario Analysis

Same Method, First Examine the Conditions

The article opens with two everyday situations: a relaxed weekend morning where you make pour-over coffee for a family member, and a rushed weekday morning where the same person must leave by 7:35 and wants the coffee by 7:28. The brewer, drinker, beans, and equipment are identical, but the time pressure changes. The key question: does the weekend routine still fit the weekday constraint?

Mission engineering requires that a scenario card explicitly capture participants, goal, time, starting conditions, constraints, and assumptions before carving out a vignette (the segment to analyze) and its measurement boundaries. Whether weekend and weekday are separate scenarios depends on whether those conditions differ; if they are the same, one card suffices.

Condition Comparison Table

Who makes/drinks: You make, same family member drinks; no extra help in either case.

When to drink: Weekend – agreed time, no immediate departure. Weekday – you can start at 7:20; family leaves at 7:35, wants coffee by 7:28.

Materials & equipment: Weekend – beans, filter papers, and home gear already on hand. Weekday – same batch of beans and same gear, but quantity and readiness must be verified.

Starting preparation state: Weekend – need to record, cannot assume everything is already set out. Weekday – assume water not boiled, beans not ground, equipment not yet at operating position.

Operation & recording: Weekend – time to check notes before start and fill records leisurely after. Weekday – you operate alone; checking notes or taking a call might cause delay, impact unknown.

With a 7:20 start and 7:28 serve deadline, the available window is 8 minutes (480 seconds). This is the target to verify. Actual start delays shrink the window further. Conditions must be recorded alongside timings so differences are not simply blamed on “rushing.”

Verified Facts, Assumptions, Constraints, and Candidate Practices

The article distinguishes four categories that are often conflated:

Verified facts – e.g., “filter papers checked, sufficient, equipment cleaned.” Record the check time; re-verify before next use.

Unverified assumptions – e.g., “no one will interrupt me these few minutes.” Mark as assumption; if interrupted, log which step was affected.

Constraints – e.g., “family must leave at 7:35” (confirmed by family) and “no new equipment this round” (self-imposed scope limit).

Candidate practices – e.g., “set up equipment the night before.” Keep as a candidate; only record as adopted after it is actually done and remains in place.

Skill level also matters: “you can make pour-over” is too vague. Distinguish between followed a tutorial a few times, can complete independently, and can record accurately under time pressure. Write the current level honestly.

Measurement Boundaries: When the Clock Starts Matters More Than Seconds Saved

If weekend timing starts after water is boiled but weekday timing starts from fetching equipment, the numbers are incomparable. The article adopts the previous episode’s scope: from deciding to prepare this cup through serving, hearing feedback, and organizing records. For the morning feasibility check, measure from the first morning preparation action to serving – including checking notes, verifying materials, fetching equipment. The 7:28 target is a plan; actual serve time is recorded. Feedback wait time is logged separately, not counted as coffee-making time. If a night-before setup is tried, its duration is recorded separately and compared alongside morning times – shifting work earlier does not mean it disappeared.

Scope Decisions

Bean purchasing and roasting are out of scope; existing bean batch and quantity are still tracked.

Post-brew cleaning is excluded from this comparison; pre-use cleanliness is a prerequisite.

If later studying “kitchen cleaned before leaving,” cleaning is added back.

Scenario vs. Vignette

Scenario : The broader context – weekday family breakfast: family must leave, you want to make coffee on time, possible counter occupation, interruptions.

Vignette : The specific segment chosen for analysis – morning preparation, brewing, and serving to see where time goes.

The selected work segment is “from preparation to serve,” not merely the 7:20–7:28 window. If actual work runs to 7:30, the extra two minutes belong to the segment and are recorded. Feedback collection and record-keeping follow, then the arrangement is judged.

Scenario Card Template

The article provides a structured card (versioned) to capture all the above. Example for weekday (CF-WD v1):

Scenario name, ID, version: Weekday pre-departure pour-over; CF-WD; v1

Objective: With current gear, can prep, brew, and serve within 7:20–7:28 (8 min)? First, find where time goes.

Participants & concerns: You – make coffee, leave reusable records. Family – taste satisfaction, time to drink.

Time, place, starting conditions: Home kitchen; plan 7:20 start, water cold, beans whole, gear not positioned; verify at start; target serve by 7:28, feasibility untested.

Segment boundaries: Overall – prep to feedback captured and records organized. Morning timing – first morning prep action to serve. Night-before prep logged separately. Record actual serve time.

Verified facts: Family confirms 7:35 departure (log date and source).

Assumptions: No interruptions; materials sufficient, gear usable – you verify before trial.

Constraints: Must not delay 7:35 departure; no new equipment this round.

Out of scope & why: No purchasing/roasting – use existing beans. Post-clean excluded from comparison; pre-use clean required.

Adjustable practices: Prep sequence, night-before gear setup, when to take notes – compare with clear starting conditions.

Open questions, who, when: Confirm taste preferences and feedback timing with family before trial; you check materials, gear, counter availability.

Unanswered items stay on the card with a plan to resolve. Versioning: if family permanently moves departure to 7:25, keep v1, create v2 with change reason, renegotiate serve target. One-off early departure goes in that brew’s record. Weekend card uses CF-WE with same fields for side-by-side comparison.

Standardized Recording Fields

Before logging data, agree on field names and formats:

Scenario ID & version, brew ID: Separate scenario ID/version (e.g., CF-WD, v1); each actual brew gets a unique ID.

Occurrence time & record time: Separate; include date and timezone. Late entries marked as recalled estimates, not precise measurements.

Duration: Start event, end event, duration, unit. Unit standardized to seconds (s); display as minutes:seconds when reading. Estimates noted with basis, not treated as measured.

Target vs. actual: Planned serve time vs. actual serve time – separate columns. Future target vs. actual temperature likewise.

Measurements & units: Temperature (°C), mass (g), volume (mL) – add as needed. Mass and volume not interchanged directly.

Source, nature, confirmation status, confirmer: Observation, measurement, or hearsay; fact vs. assumption; who confirmed, what remains unverified.

Missing data reason: Not measured, not recorded, not applicable – distinct from zero or “normal.”

Example: served at 7:27, noted in evening → occurrence time 7:27, record time evening. If only approximate, label “recalled estimate.”

Apply to Your Work

Pick a 1–3 day observable task (e.g., spare-part pickup, manual test-environment release). Find two condition variants (normal vs. urgent near shift end). Use the blank card template below, fill each field, then review with a participant: will they be available when needed? Which conditions are still guesses? Does total elapsed time include prep? Clarify fuzzy points before comparing methods.

Scenario name, ID, version:
Objective:
Participants & concerns:
Time, place, starting conditions:
Segment boundaries:
Verified facts & sources:
Assumptions:
Constraints:
Out of scope & why:
Adjustable practices:
Open questions, who, when:

Summary

Weekend allows time for notes and leisurely records; weekday mornings may demand pre-arrangement. Writing conditions explicitly lets anyone later understand under what circumstances “this method works.” Next, with the 8-minute target, we’ll examine whether on-time serving and family consumption mean the coffee is “done” – evaluation criteria, confirmation authority, and required records.

Reference

U.S. Department of Defense, Mission Engineering Guide, Version 2.0, 2023-10-01. Primarily Chapter 4 and Section 4.1, printed pages 12–14: Mission Context, Scenario and Vignette, Assumptions, Constraints, and Scope Limits. The coffee context, time settings, card, and field conventions are teaching designs, not prescribed templates or coffee standards. https://ac.cto.mil/wp-content/uploads/2023/11/MEG_2_Oct2023.pdf