C.W.K.
Stream
Lesson 04 of 04 · published

Low-Trigger by Design

~12 min · emotional-design, north-star, structure-over-willpower, invariant

Level 0Open Gate
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete
"The best investing decision is usually to do nothing. So I built a tool that makes doing nothing feel normal."

The invariant is a feeling

Every serious system has a north star — the one thing every other decision serves. For most portfolio apps it's engagement: more opens, more checks, more trades. Keep's north star is the opposite, and it's stated as a feeling, not a feature: low-trigger monitoring — preserve useful information and provenance while reducing the impulse to react. That sentence is a design constraint on the whole surface, not a mode you toggle. When any later decision is ambiguous, this is the tiebreaker: the option that lowers the trigger wins.

Structure beats willpower

Here's the psychology Dad built it around. Everyone knows they shouldn't panic-sell on a red day or chase a green one. Knowing doesn't help — because the app itself is manufacturing the panic. A blinking loss, a big red number, a push notification, a leaderboard of "today's movers" — these aren't neutral information, they're triggers engineered to convert your attention into action. Willpower against a machine built to defeat willpower is a losing game. So Keep doesn't ask you to resist the triggers. It removes the triggers. You can't panic at a number that was never made scary in the first place.

Don't build a temptation and then ask for discipline. If the correct behavior requires the user to constantly resist the interface, the interface is the problem. Design the calm behavior as the path of least resistance, and willpower becomes unnecessary — which is the only way it reliably works.

What 'low-trigger' actually changes downstream

This isn't a slogan that stays in the README. It has teeth in nearly every track ahead:

  • Observe, never advise — the app states facts and never scores a trade, so there's nothing to obey.
  • Values over color — red and green are secondary to plain numbers, dates, and sources, so the palette can't shove you.
  • Pause by default — the live price stream is off until you deliberately turn it on; the resting state is a calm durable close, not a twitching tick.
  • Stale stays visible — old data is labelled, not hidden or urgently refreshed, so nothing screams "act now."

Each of those is a separate engineering decision, and every one of them traces straight back to this single sentence.

This is Dad's investing philosophy compiled into software. He treats good investing as mostly not acting — hold quality, ignore the noise, let structure carry you past the moments willpower fails. Keep is that belief rendered as an app: the calm isn't a wellness feature bolted on top, it's the architecture. The tool embodies the discipline so the person doesn't have to summon it.

Code

The tiebreaker, written as a rule·text
When two designs are otherwise equal, choose the one that
lowers the trigger.

  bigger red number            ->  rejected (raises the trigger)
  push alert on a 3% move       ->  rejected (raises the trigger)
  "top movers today" ranking    ->  rejected (raises the trigger)
  value + date + source, muted  ->  chosen   (preserves info, low trigger)
  streaming paused by default   ->  chosen   (calm at rest)

# The north star isn't advisory. It decides real feature fights.

External links

Exercise

Name your own 'do nothing' domain — a place where the right move is usually restraint (eating, spending, doomscrolling, checking a metric). Now describe the interface that surrounds it. Is it low-trigger or high-trigger? List two specific elements engineered to make you act, and redesign each one so the calm behavior becomes the path of least resistance instead of requiring willpower.
Hint
The test: could someone with zero discipline use this and still land on the calm behavior most of the time? If staying calm requires constant self-control, the design is doing the opposite of its stated goal — it's outsourcing its job to the user's willpower.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.