Launch Briefing | COSMOS | Learning Rewired Lab

Diagnose the request before you build the rocket.

A suspicious training request has entered mission control. Your job is to slow down, classify the signal, scan the system, choose a stronger behavior target, and earn clearance from Captain Strato.

Step 01

Classify the signal.

What is the strongest first read on this request?

Clear training need The managers just need to learn feedback best practices. Suspicious training request The request may be valid, but we need to diagnose the performance problem first. Content gap Managers probably need a better explanation of the feedback model.

Step 02

Scan for the real problem.

What should you investigate before building anything?

Workflow, expectations, practice, and feedback conditions Look for what makes feedback hard in the real manager workflow. Available slide content Find existing materials and turn them into a cleaner module. Completion requirements Decide how long the module should be and who needs to finish it.

Step 03

Choose the behavior target.

Which target gives the design work the clearest direction?

Managers understand feedback principles. Focus on knowledge and awareness. Managers hold timely, specific feedback conversations after key work moments. Focus on observable performance. Managers complete the required feedback module. Focus on participation.

Step 04

Recommend the solution mix.

What is the strongest next design recommendation?

A short module with examples and a quiz Better than nothing, but still course-shaped. Brief instruction, scenario practice, manager prompts, and follow-up evidence Design the learning system around the behavior. A polished explainer video Easy to consume, but unlikely to change feedback behavior alone.

Systems Scan moves from request diagnosis to environment diagnosis.

In Launch Briefing, you learned to slow down before accepting the training request. In Systems Scan, you inspect the work environment for the forces shaping behavior: manager signals, workflow friction, unclear criteria, missing practice, weak feedback loops, incentives, and suspicious pig anomalies.

Diagnose the request before you build the rocket.

“Can we make a quick module so managers give better feedback?”

Complete the diagnostic sequence.

Classify the signal.

Scan for the real problem.

Choose the behavior target.

Recommend the solution mix.

The first design move is not building. It is diagnosing.

Systems Scan moves from request diagnosis to environment diagnosis.