Computer Impressions · Internal Training System

Applied Hyper-Learning
All 7 Frameworks

A field-tested system for turning new hires into trusted contributors — and trusted contributors into leaders who build others.

Phase 1 · Learn the Basics
Phase 2 · Learn to Produce
Phase 3 · Learn to Thrive

Culture doesn't come from what you do. It comes from what you build other people to do.

— Jesse Salmon · Computer Impressions
The 7 Frameworks
Core Operating System
1
The Handoff
New hires work silently. Managers fill silence with anxiety.
Core Idea

A: Echo it back — Repeat the task in your own words. 2–3 rounds until you're aligned.


B: Set the timeline — Give a specific time, not a vague range. Name the deliverable exactly.


C: Check in before the deadline — Not after. Not when you're stuck. Before.

The One Thing to Remember
The check-in before the deadline is worth more than the deliverable itself. Deliver exactly what was negotiated — not more, not less.

When This Fails
When the team member doesn't echo the task back, deliverables show up that don't match what was agreed. Managers spend Monday re-doing the negotiation they thought happened Friday — and stop trusting the next "yes."
2
Agile Stand-Up Answer
Progress updates are either rambling or useless.
Core Idea
  1. What I completed
  2. What I have left
  3. What is blocking me (+ 2 guesses at the answer)

15-second version or 2-minute version — read the room.

The One Thing to Remember
Calibrate to their time. Ask: "Quick version or full version?" Then deliver. Your manager doesn't care what you're doing — only what's done and what's left.

When This Fails
When the team member skips the sixty-second summary, status updates become ten-minute monologues. The manager tunes out. Blockers get buried in narration, and the team can't tell what's actually stuck from what's just being narrated.
3
Problem-Solving Sequence
Jumping to solutions before understanding the problem.
Core Idea
  1. Define clearly
  2. Form a hypothesis
  3. Find the fastest verification path
  4. Run the test
  5. Communicate the finding

Check data before code. Test one example first.

The One Thing to Remember
"I checked school 5067. Source: 9%. Output: 9%. Match. Code correct." — State findings clearly. The finding is the deliverable, not the investigation.

When This Fails
The team member does the work but skips the report. The manager assumes nothing is moving. The team duplicates effort because the finding never circulated, and the lesson dies inside one head.
4
Decision-Making Discipline
Asking the manager about things you could figure out yourself.
Core Idea

A: You can determine it — Go find it. Don't ask.


B: You can guess — Present it with your reasoning attached.


C: Genuinely don't know — Ask, framed as verification. Always bring a guess first.

The One Thing to Remember
Managers hired you so they wouldn't have to make every decision. Closed questions with a guess are easy to answer. Open questions drain time.

When This Fails
The team member waits for permission on every minor call. The manager becomes the bottleneck. Small decisions queue up. Velocity collapses not because the work is hard, but because nothing moves without sign-off.
5
First Pass vs. Best Practice
Perfectionism on the first attempt creates tech debt and paralysis.
Core Idea

Best Practice: Done correctly, to standard. Takes time. Right context.


Quick & Dirty: Fast, intentional, with notes written. Right context.


The Middle: NEVER. That's where tech debt lives.


Consistency > Originality at work. Every blank stops the team.

The One Thing to Remember
Success = honoring your agreement + getting better every day. Not perfection. A wrong guess that's documented is more valuable than a blank.

When This Fails
The team member leaves blanks instead of plausible guesses. Every blank stops the team and forces the manager to re-enter the work — the assignment effectively didn't happen, and the manager carries the cost twice.
6
Win / Win / Win
Saying yes to everything leads to burnout and broken promises.
Core Idea

Win 1 — The Work: The customer gets what they need, to standard.


Win 2 — The Company: Computer Impressions can deliver on promises without margin erosion.


Win 3 — You: You can deliver without burning out. Your health is not a sacrifice.


If any win is missing — renegotiate first.

The One Thing to Remember
Renegotiate before you commit — not after you fail. Saying yes when the third win is missing doesn't create goodwill. It trains clients to expect more and value you less.

When This Fails
The team member says yes to everything, then quietly fails two weeks later. The manager learns about the cost only when the deliverable misses or someone burns out. Trust erodes through silent failure, not honest pushback.
7
The Unstuck Sequence
Getting stuck leads to silence, paralysis, or premature escalation.
Core Idea
  1. Name it — Write "I am stuck on ___"
  2. Rotate tasks — Keep moving. Never stop.
  3. Two guesses — Break paralysis before asking.
  4. Clarify — Write it, say it, explain it to someone.
  5. Send the message — Guesses + question + what you tried.
The One Thing to Remember
You are never stuck. You are working, rotating, guessing, clarifying, or sending. One of those is always available to you right now.

When This Fails
The team member freezes when stuck, and hours disappear with nothing to show. The freeze is invisible to the manager — until stand-up reveals zero progress and the time is already spent.
Supporting System
Self-Trust Tools

Four tools that build confidence through self-knowledge — not external validation. These don't replace the frameworks. They make you better at using them.

Min / Max Task Estimation
Set a minimum and maximum time for each task — you set them, no one else. At the minimum mark, ask: "Can I finish within max?" Yes → keep going. No → rotate. This is how you build a track record you can trust.
Parallel Tasks
Always have 3–5 active tasks running at once. Getting stuck on one is the signal to rotate — not to stop. Stopping is the only real failure state. Rotating keeps value flowing.
The Parking Lot
Good idea outside your agreement? Write it down. Don't act on it. After 20 years in the field: most items are still there when the project ends. Ideas that survive the parking lot are worth pursuing.
Daily Debrief
One question, every day: "How do I get it better next time?" — even when it went well. Built in daily, not reserved for failure. This is how professionals turn experience into expertise.
Applied Hyper-Learning  ·  Jesse Salmon  ·  Computer Impressions  ·  Field-tested. Not theory.