---
title: "Connect information to outcomes"
pattern_id: "connect-information-to-outcomes"
trait: "Invested"
type: "Humorphic pattern brief for coding agents"
spec_version: 3
canonical_url: "https://humorphism.com/patterns/connect-information-to-outcomes"
markdown_url: "https://humorphism.com/patterns/connect-information-to-outcomes.md"
index: "https://humorphism.com/llms.txt"
all_patterns_in_one_file: "https://humorphism.com/llms-full.txt"
normative_section: "Rules"
rule_prefix: "CIO"
rule_ids: ["CIO-R1", "CIO-R2", "CIO-R3", "CIO-R4", "CIO-R5", "CIO-R6", "CIO-R7", "CIO-R8", "CIO-R9"]
---

# Connect information to outcomes

## How to read this file

You are an agent. Someone gave you this file so you can add one behavior to their product: the AI teammate in it should report every number, alert, and recommendation as progress toward the person's goal, and say what each one means for that goal. This file is the complete specification for that behavior. Build from it.

**The Rules section is the only normative part.** Everything else exists to make the rules buildable: the capabilities tell you which parts of the pattern the product can support, the reference screens show you the behavior in motion, the examples give you four shapes it can take, and the checklist is how you confirm you are done. Examples and the checklist point back to rule IDs rather than restating requirements, so each requirement lives in exactly one place. If any other section seems to contradict a rule, the rule wins.

Work in this order:

1. **Find where this belongs** in the product: any dashboard, report, or status update the product shows, the moment an alert or signal would fire, and any periodic summary of what the AI teammate has done.
2. **Read Rules.** All nine apply to whatever you build.
3. **Check Capabilities** against what the product already has. Build the examples its capabilities support, and take the stated fallback for the rest.
4. **Pick your examples.** If you build only one, build Example 3.
5. **Build it in the product's own design system, components and voice.** The reference screens say what each screen does and why. They are not a specification of how it must look. Keep the behavior, change the expression.
6. **Confirm against the checklist** before you call it done.

Humorphism is a design philosophy for products with AI in them. It replaces the user interface, built for operating tools, with the human interface, built for collaborating with AI teammates. There are 21 humorphic patterns grouped into 7 traits. You do not need the others to build this one, but if you can fetch URLs: [llms.txt](https://humorphism.com/llms.txt) lists every humorphic pattern with a one-line summary and a link, and [llms-full.txt](https://humorphism.com/llms-full.txt) has all of them in one file.

## The pattern

_Trait: Invested. Aligns with the person’s goals and cares whether they succeed_

A good AI teammate reports progress against the goal rather than activity. Every number, alert, and recommendation says what it means for the person’s goal.

**Build this.** An AI teammate ties every number to the goal it moves and tells the person about opportunities that accelerate that goal.

**Avoid this.** A tool fires raw alerts and usage totals, because it measures what it can count rather than what the person is trying to do.

The difference to carry into your build:

| Tool | AI teammate |
|---|---|
| Measures what it can count | Measures against what the person is trying to do |
| Every metric at equal weight | The one number that moves the goal, first |
| The person does the math | A sentence says whether they are on track |
| Raw alerts to triage | Openings framed as progress, with the first step ready |
| Reports activity and hours | Reports outcomes in the person's business terms |
| The goal freezes at setup | New goals are proposed when the evidence points to them |

## Rules

Normative. All nine hold for everything you build from this file. Each one says what to do, why it matters, and what it looks like once it is built.

| ID | Rule | Why | Built correctly when |
|---|---|---|---|
| **CIO-R1** | Measure every number against the person's own goal, the one they set or adopted, not a generic benchmark or last period alone. | A number only means something to the person relative to what they are trying to achieve. | Each number shown names the goal it is measured against, and that goal is one the person set or adopted in the product. |
| **CIO-R2** | Lead with the number that moves the goal. Keep the rest one step away. | Four figures at equal weight hand the person the job of deciding which one matters. | The first and largest number on the screen is the one the goal depends on, and other metrics are not shown beside it at equal weight. |
| **CIO-R3** | Say in one plain sentence where the goal stands: on track or not, and what remains. | The person should know whether they are on track without doing the math. | Every goal number is accompanied by a one-line verdict that names the goal, its target, and the gap or time left ("On track for your Q3 goal of 12% with 3 months to go"). |
| **CIO-R4** | Present a signal as a step toward the goal: how far it moves the goal, with the first step already prepared. | A signal with its effect and its next step is progress to make; without them it is one more alert to triage. | An opportunity states its effect on the goal ("would close 8% of the gap") and carries one action that takes the prepared step, a way to see what was prepared before taking it, and a way to set it aside. |
| **CIO-R5** | Report the AI teammate's own impact in the person's business units, not in activity. | Counts of tasks or hours do not tell the person what the AI teammate is worth to them. | The AI teammate's report leads with dollars, time, or deadlines in the person's terms, and activity counts appear only as the basis for those figures. No figure is counted in people's hours, headcount, or pay. |
| **CIO-R6** | Show how every derived number was counted, one action away. | A number the person cannot inspect or challenge is a claim, not a report. | Every total, estimate, or projection has a way to see its inputs and method ("How I counted"). |
| **CIO-R7** | Propose a new goal when repeated behavior or outside evidence points to one, with the evidence, and let the person adopt, edit, or dismiss it. | A goal set that never changes stops matching the business. | A proposed goal shows its evidence and three choices (adopt, edit, dismiss), and nothing is tracked against it until the person adopts it. |
| **CIO-R8** | Keep the goal editable from where its numbers appear, and reframe the numbers when it changes. | Numbers framed against an outdated goal mislead with confidence. | The person can change or remove the goal next to the numbers it frames, and every verdict updates to the new goal at once. |
| **CIO-R9** | Speak only when the goal's outlook changes. | A stream of updates about movement that changes nothing is the tool's raw alerts with friendlier words. | No message or alert fires for a change that leaves the goal's outlook the same. |

**CIO-R1 carries the pattern.** Connect the numbers to the goal the person actually holds, stored in the product, before you write a single verdict. A build that misses CIO-R1 frames numbers against nothing in particular: it adds friendly captions to the tool's dashboard and reads like the pattern while measuring what it can count.

## Capabilities

Build the examples the product's capabilities support. Do not stub a capability the product lacks, and do not write copy that implies one it lacks.

| Capability | What it is | Used by | If the product lacks it |
|---|---|---|---|
| Memory | A place that keeps facts, preferences, rules, and open threads across sessions. The person can see everything the AI teammate remembers and edit or delete any of it. | Example 1, and keeping a goal adopted in Example 4 across sessions | Ask for the goal at the start of the session and frame numbers against it for that session only, and say so. Do not claim to track progress over time or to remember the goal next time. |
| Monitoring | Baselines and thresholds on the signals the person cares about, plus the last-seen state, so the AI teammate can say what changed. | Example 2 | Frame only the numbers the product already shows, against the goal, when the person looks at them. Do not claim to watch for signals or to say what changed since last time. |

Examples 3 and 4 need none of these. **If you build only one example, build Example 3.**

## Reference screens

These describe the animations on the pattern page frame by frame, so you can build from this file alone. They show the behavior, not the appearance to copy. **Keep the behavior, change the expression:** build in the product's own design system, components, type and voice.

One convention to translate rather than reproduce. On these screens the AI teammate speaks from a light gray band attached to the card: below the chart on the pattern screen and above the card in two of the examples, with a small orange square at the head of its line. Elsewhere the square sits at the head of the AI teammate's line or label. The AI teammate's side sits on a warm, slowly moving gradient while the tool's side sits on flat gray. The goal itself is drawn as a dashed line on a chart or a marker at the end of a progress bar. Choices arrive as light gray buttons of equal width, and the person's choice registers as the pressed button turning black. Use whatever your system already uses for "the AI teammate is speaking", "this is the goal", "this is the suggested action" and "this was chosen".

### The AI teammate version (frames 01 and 02, a loop of about 5 seconds)

One white card, centered on a warm, slowly moving gradient of pink, orange and blue. At the top left, a small gray label, "Conversion", then the figure "9.8%" in large type, and under it in small text "↑ 1.7% this month". Below that, a wide chart with no axes: a dashed orange line near the top marks the goal, and a single gray line with a soft gray fill under it climbs from the lower left toward it. Under the card and attached to it, a light gray band with the orange square and the line "On track for your Q3 goal of 12% with 3 months to go".

There is no person in this screen and nothing to press.

The loop starts with the white card as a thin strip. It grows to its full height in one smooth motion while its contents fade in, in reading order and quickly: the "Conversion" label, "9.8%", "↑ 1.7% this month", then the chart with its goal line. Once the card is full, the gray band rises from under its bottom edge as a small rounded bubble holding only the orange square, widens to the card's width, and the message arrives one word at a time: "On track for your Q3 goal of 12% with 3 months to go". The end state holds for about 3.5 seconds, then the loop restarts on the thin strip.

What to take from it: the AI teammate shows one number, the one the goal depends on, named by that goal and drawn against it (CIO-R1, CIO-R2). It then says in one line whether the goal is on track, what the target is, and how much time is left, so no math is needed (CIO-R3). And it says that once, without an alert (CIO-R9).

### The tool version (frame 03, a still screen with no motion)

A square-cornered white card on a flat light gray background with no gradient. No orange square, so nothing on screen speaks as an AI teammate. At the top left, "Dashboard" with a small tinted "3 alerts" tag beside it, and at the top right a "Last 30 days ▾" filter. Below, four figures in a row at equal weight, each with a label above and a change below: "Trials" "1,284" "+3.2%", "Paid" "126" "+1.1%", "Conversion" "9.8%" "+1.7 pts", and "Churn" "2.1%" "−0.4 pts". Under them, a legend for "Conversion", "Trials" and "Paid", and a chart of three unfilled gray lines, one of them dashed, over a grid.

The conversion number and its trend are the same as on the AI teammate screen. Nothing says which number matters, what the goal is, or whether anything is on track.

What to take from it: the dashboard measures what it can count rather than what the person is trying to do (CIO-R1), gives every figure equal weight (CIO-R2), and leaves the person to work out whether they are on track (CIO-R3). The alerts arrive as a count with no meaning attached (CIO-R9). This is the shape to move away from.

## Examples

Each example is one way to apply the pattern in a real product. They are not steps in order, and no product needs all four. Pick the ones that fit the moment and the data the product has.

Each is written as one exchange in four beats: **Cue** (the moment in the product when the AI teammate should act), **Move** (what the AI teammate does), **Response** (what the person does in return), **Resolution** (where things stand afterwards).

"Satisfies" names the rules this example is responsible for.

### 1. Here’s how we’re tracking (Frame numbers as progress)

A colleague giving an update says “on track for Q3” rather than reading out last month’s totals.

- **Cue:** A metric, alert, or report is about to be shown
- **Move:** Frames each number as progress toward the goal, the way “on track for Q3” does.
- **Response:** Drills into the metric, or adjusts the goal it’s measured against
- **Resolution:** The person knows whether they’re on track without doing the math
- **Needs:** Memory.
- **Reference frame 04:** a light gray band across the top of a white card, with the orange square and the line "On track for your Q3 goal". In the card, a small gray label "Trial-to-paid conversion", the figure "9.8%" in large type, and a progress bar whose black fill runs about four fifths of the way to a short upright mark at its right end, labeled "Q3 goal 12%". Under the bar, in small text, "↑ 1.7 points this month". In the animation the orange square fades in, and the band's line fades in whole just after it. The label rises in, "9.8%" pops in, the "Q3 goal 12%" flag rises in, and the bar's fill grows from the left to where it rests. "↑ 1.7 points this month" rises in last. The card holds for about 3.5 seconds, then the loop restarts. The verdict comes first, and the number is shown as distance to the goal rather than as a total.
- **Sample lines:** "On track for your Q3 goal: conversion is 9.8%, and 12% is within reach at this month’s pace." / "At this pace the Q3 goal falls short by about a point. I can show what would close it." / "You changed the goal to 11%, so you’re now ahead of plan."
- **Satisfies:** CIO-R1, CIO-R2, CIO-R3, CIO-R8.

### 2. This gets you closer (Frame a signal as a step toward the goal)

A colleague who knows your target flags an opening as “this gets you closer to the Q3 number,” not as one more alert.

- **Cue:** A signal appears that could move a stated goal: a warm lead, a lapsed account, an unused credit
- **Move:** Presents a signal as an opportunity: how far it moves the goal, with the first step ready
- **Response:** Takes the step, saves it for later, or says the goal has changed
- **Resolution:** Signals read as progress the person can make, not as noise to triage
- **Needs:** Monitoring.
- **Reference frame 05:** the orange square and the line "Turning on annual billing would close 8% of the gap to your Q3 goal." at the top of a white card on flat gray, with "8%" in bold orange. Under it, in smaller gray text, "I set up the plans, prices, and checkout copy." Under that, two buttons of equal width side by side, "Later" and "Turn it on". In the animation the square swells once and the line arrives word by word, the gray line rises in beneath it, and both buttons rise in, light gray. The cursor glides up from the lower right to "Turn it on", the button darkens on hover, and on the click it turns black. The cursor and its hover fade away, and the card holds for about 3.5 seconds, then the loop restarts. The signal is sized against the goal, the first step is already done, and taking it is one press. On the screen, "Turn it on" puts the plans and prices live before the person has seen them; in a build, let the person see them before taking the step (CIO-R4).
- **Sample lines:** "Turning on annual billing would close 8% of the gap to your Q3 goal. I set up the plans, prices, and checkout copy." / "No problem, I’ll keep it ready and bring it back if the gap grows." / "Since your goal changed, this no longer moves it much, so I’ve set it aside."
- **Satisfies:** CIO-R1, CIO-R4, CIO-R9.

### 3. Here’s how I helped (Report impact in the person’s units)

In a status meeting a colleague says what they moved for the team, not how many hours they logged.

- **Cue:** A reporting cadence comes due, or the person asks what the AI teammate has done.
- **Move:** Reports outcomes in the person’s business terms, such as dollars saved or a deadline met sooner.
- **Response:** Inspects how a number was derived, or challenges it
- **Resolution:** The AI teammate’s value is legible in business terms
- **Needs:** nothing beyond the AI teammate itself.
- **Reference frame 06:** a light gray band across the top of a white card, with the orange square and the line "What I saved you this month". In the card, a three-column table separated by thin dividers: "Refunds handled" "312" "$14.0k", "Duplicate invoices caught" "18" "$9.2k", "Hours reclaimed" "41 h" "$6.8k", and a bold last row "Total" "$30.0k". Under the table, a small underlined link, "How I counted". In the animation the orange square fades in, and the band's line fades in whole just after it. Then the table rises in a row at a time from the top, the total last, and "How I counted" rises in under it. There is no cursor. The card holds for about 3.5 seconds, then the loop restarts. The activity counts are there, but every row ends in dollars, the total leads in the person's units, and the method is one click away. The one part not to copy is the "Hours reclaimed" row and the $30.0k total that includes it: that row counts people's hours and prices them at pay rates, which CIO-R5 rules out. Without it, the total is $23.2k.
- **Sample lines:** "I saved you $23.2k this month, most of it from refunds I handled." / "Here’s how I counted the refunds: 312 refunds handled, at their average value of about $45." / "You’re right, the duplicate invoices would have been caught at month end anyway. I’ve taken them out, so it’s $14.0k."
- **Satisfies:** CIO-R5, CIO-R6.

### 4. We could aim even higher (Suggest a new goal)

A colleague who has noticed a pattern floats a new target in passing: “have you thought about tracking onboarding time?”

- **Cue:** Repeated behavior or external trends point at a goal the person hasn’t stated
- **Move:** Proposes a new outcome to track, with the evidence for it
- **Response:** Adopts it, edits it, or dismisses it
- **Resolution:** The goal set evolves with the business instead of freezing at onboarding
- **Needs:** nothing beyond the AI teammate itself.
- **Reference frame 07:** the orange square and a small gray label, "Proposed goal", at the top of a white card. Under it, the title "Onboarding under 10 minutes", then two bullet points of evidence: "Today’s median is 18 minutes." and "Teams that finish in 10 convert twice as often." Under that, three buttons of equal width in a row: "Dismiss", "Edit" and "Track it". In the animation the orange square and the label rise in together, the title arrives word by word, the two bullets rise in one after the other, and the three buttons rise in, light gray. The cursor glides up from the lower right to "Track it", the button darkens on hover, and on the click it turns black. The cursor and its hover fade away, and the card holds for about 3.5 seconds, then the loop restarts. The new goal arrives as a proposal with its evidence, and adopting, editing, and dismissing are each one press.
- **Sample lines:** "Teams that finish onboarding in 10 minutes convert twice as often. Should I track that as a goal?" / "Tracking it. I’ll report onboarding time alongside conversion from now on." / "Dismissed. I won’t raise it again unless the numbers change."
- **Satisfies:** CIO-R7.

## Edge cases

- **No goal set.** Do not invent one; show the numbers plainly, say there is no goal to measure them against, and offer to set one (CIO-R1).
- **The person sets it aside.** When the person presses "Later" or ignores an opening, keep it without raising it again until the goal's outlook changes (CIO-R9).
- **A proposal dismissed.** Track nothing against a dismissed goal and do not propose it again unless new evidence appears (CIO-R7).
- **A wrong number.** When the person challenges a figure, show how it was counted and correct the total in place if the challenge holds (CIO-R6).
- **The goal changes.** Reframe every number and verdict against the new goal at once, and drop openings that no longer move it (CIO-R8).
- **Off track.** Say plainly that the goal is off track and by how much, rather than leading with whatever moved up (CIO-R3).

## Related patterns

These overlap with this one. Do not ask the same thing twice across them, and when you apply several humorphic patterns to one product, count every update, alert, and opening the AI teammate raises against one goal across all of them, and hold that total to CIO-R9 rather than each pattern on its own.

- [Understand the person’s goals](https://humorphism.com/patterns/understand-the-persons-goals.md): learns the goal that every number here is measured against.
- [Have a point of view](https://humorphism.com/patterns/have-a-point-of-view.md): picks the one recommendation to lead with, where this pattern frames the numbers behind it.
- [Contribute without being summoned](https://humorphism.com/patterns/contribute-without-being-summoned.md): raises an opening unasked, where this pattern sizes it against the goal.
- [Show your work](https://humorphism.com/patterns/show-your-work.md): shows the sources and reasoning behind a reported number in full.

## Checklist

Confirm each one before you call this built. Each item is the rule it comes from.

- [ ] CIO-R1: Each number shown names the goal it is measured against, and that goal is one the person set or adopted in the product.
- [ ] CIO-R2: The first and largest number on the screen is the one the goal depends on, and other metrics are not shown beside it at equal weight.
- [ ] CIO-R3: Every goal number is accompanied by a one-line verdict that names the goal, its target, and the gap or time left ("On track for your Q3 goal of 12% with 3 months to go").
- [ ] CIO-R4: An opportunity states its effect on the goal ("would close 8% of the gap") and carries one action that takes the prepared step, a way to see what was prepared before taking it, and a way to set it aside.
- [ ] CIO-R5: The AI teammate's report leads with dollars, time, or deadlines in the person's terms, and activity counts appear only as the basis for those figures. No figure is counted in people's hours, headcount, or pay.
- [ ] CIO-R6: Every total, estimate, or projection has a way to see its inputs and method ("How I counted").
- [ ] CIO-R7: A proposed goal shows its evidence and three choices (adopt, edit, dismiss), and nothing is tracked against it until the person adopts it.
- [ ] CIO-R8: The person can change or remove the goal next to the numbers it frames, and every verdict updates to the new goal at once.
- [ ] CIO-R9: No message or alert fires for a change that leaves the goal's outlook the same.
- [ ] Capabilities the product lacks were skipped honestly, not stubbed or implied.
- [ ] It is built in the product's own components and voice.

## Images

Stills from the animations on the [pattern page](https://humorphism.com/patterns/connect-information-to-outcomes), shipped alongside this file. The Reference screens and Examples sections describe each one in full, so this file works without them.

| File | Shows | Described in |
|---|---|---|
| [01-teammate-the-number-against-the-goal.png](https://humorphism.com/patterns/connect-information-to-outcomes/01-teammate-the-number-against-the-goal.png) | The conversion number and its line heading for the dashed goal line | AI teammate version |
| [02-teammate-says-where-the-goal-stands.png](https://humorphism.com/patterns/connect-information-to-outcomes/02-teammate-says-where-the-goal-stands.png) | "On track for your Q3 goal of 12% with 3 months to go" under the chart | AI teammate version |
| [03-tool-dashboard.png](https://humorphism.com/patterns/connect-information-to-outcomes/03-tool-dashboard.png) | Four figures at equal weight, three trends at equal weight, and 3 alerts | Tool version |
| [04-example-heres-how-were-tracking.png](https://humorphism.com/patterns/connect-information-to-outcomes/04-example-heres-how-were-tracking.png) | Trial-to-paid conversion at 9.8% on a bar that ends at the Q3 goal of 12% | Example 1 |
| [05-example-this-gets-you-closer.png](https://humorphism.com/patterns/connect-information-to-outcomes/05-example-this-gets-you-closer.png) | An annual billing opening sized as "8%" of the gap, with "Turn it on" pressed | Example 2 |
| [06-example-heres-how-i-helped.png](https://humorphism.com/patterns/connect-information-to-outcomes/06-example-heres-how-i-helped.png) | A $30.0k total broken down by row, with "How I counted" under it | Example 3 |
| [07-example-we-could-aim-even-higher.png](https://humorphism.com/patterns/connect-information-to-outcomes/07-example-we-could-aim-even-higher.png) | A proposed goal, "Onboarding under 10 minutes", with its evidence and "Track it" pressed | Example 4 |
