Daily Life · Chapter XVI · 2026-09-14

The Distance Between Is and Could Be

How to turn dissatisfaction into design instead of frustration

Opening Note — The Gap Is Not the Enemy

There is a small sentence hidden underneath almost every act of improvement: this could be better.

The room could flow better. The sofa could sit better. The proposal could explain itself faster. The team could hand information over more clearly. Your mornings could contain less reaction. Your money could be organized with more intention. Your career could move toward work that uses more of your real abilities.

That gap between what exists and what you prefer can create two different lives. In one, it becomes chronic irritation. In the other, it becomes design material.

You learn to describe the present accurately, define a preferred condition, identify what is actually under your influence, and make the next move small enough to test. You stop requiring certainty before action. You stop confusing a better future with a perfect future.

This chapter is about agency—not the motivational version where you pretend everything is under your control, but the practical version where you become skilled at changing the part that is.

1. Describe the Present Without Drama

Improvement begins with an accurate description of what exists.

People often describe situations through judgment: “Production is a mess.” “The client is difficult.” “The design feels cheap.” “I have no time.” These may contain real frustration, but they are poor design inputs.

Translate judgment into observable conditions.

Instead of “production is a mess,” perhaps: final dimensions arrive after cutting begins, two versions of the drawing circulate simultaneously, and finish approvals live inside separate message threads.

Instead of “the room feels cheap,” perhaps: five materials compete at the same visual intensity, wood grain scale is inconsistent, lighting is flat, and hardware is visually heavier than the cabinet fronts.

Specificity reduces helplessness. A useful designer does not deny emotion. They translate emotion into information.

**Exercise — The Camera Test:** Choose one situation you want to improve. Write your complaint. Then rewrite it as if a silent camera, calendar, drawing set, invoice, or message history had to prove every sentence.

2. Define Preferred Before Perfect

Once you can see the present clearly, the next question is not “What would be ideal?” Ask: “What would be meaningfully better?”

Perfect futures are often too abstract to design. Preferred futures can be concrete.

A perfect handover might mean zero surprises. A preferred handover might mean every room has one approved specification sheet, final site dimensions are signed off before production, and unresolved items are visibly marked rather than silently assumed.

A perfect routine might contain training, reading, language learning, content creation, excellent work, and perfect sleep every day. A preferred next version might mean three protected workouts, twenty minutes of language practice on four days, and one two-hour creative block on the weekend.

**Practice:** Write the current state, the preferred state in thirty days, and the evidence that would prove the change happened. If you cannot observe success, the goal is still too vague.

3. Find the Smallest Lever

Not every improvement requires a large intervention.

A lever is a small change that alters many downstream decisions. A standard site-measurement sheet can prevent repeated production questions. One naming convention can stop teams from fabricating from outdated files. A signed fabric sample can prevent arguments after upholstery.

Look for repeated friction. If the same mistake appears three times, do not only correct the third instance. Ask what upstream condition makes the mistake easy to repeat.

This is where design becomes more powerful than effort. Effort solves the visible case. Design changes the conditions that generate cases.

You can remind everyone to check grain direction on every job. Or you can add a mandatory grain-direction arrow to the drawing template. The second solution stores intelligence in the system.

**Exercise — Upstream Five:** Choose one recurring problem and ask “What made this possible?” five times. Find the earliest practical condition you can change.

4. Prototype the Future Before You Defend It

People become attached to ideas when they spend too long explaining them. Testing is healthier than defending.

If you think a new proposal format will help clients understand packages, build one page and watch someone use it. If a new sofa depth should improve comfort, create a rough full-scale test. If educational videos could become a meaningful career asset, publish ten before building an elaborate content system.

A prototype turns an argument into evidence. The question changes from “Was my idea good?” to “What did this version teach us?”

Prototype cheaply enough that being wrong is affordable.

This is especially important with AI. Generation makes polished concepts cheap, but polish can trick people into defending a direction before cost, comfort, construction, demand, and maintenance have been tested.

**Reflection:** Where are you currently explaining an idea that you could test instead? Design one test that can happen in less than a week.

5. Decide Where Not to Improve

Agency does not mean fixing everything.

Every project contains more possible improvements than budget, schedule, attention, and people can support. Mature design includes deciding what will remain imperfect.

Rank improvements by consequence. Does this reduce meaningful risk? Noticeably improve the user's experience? Create reusable knowledge? Strengthen the business? Is the cost proportionate to the benefit?

If the answer is no across all of them, the improvement may be attractive but not important.

Perfectionism treats every flaw as morally equal. Professional judgment does not.

**Practice — The Not-Now List:** For one project, write three improvements you are deliberately not making in this version and why. This converts accidental neglect into conscious scope.

6. Build Feedback Into the Change

A preferred future is only a hypothesis until reality responds.

If you change a proposal, notice whether clients ask fewer clarification questions. If you change a sofa cushion, sit on the prototype after ten minutes, not only for a photograph. If you change a team process, check whether people actually use it after two weeks.

Feedback should be close to the action. The longer the delay, the harder it becomes to understand cause and effect.

Do not measure everything. Measure the uncertainty. If the uncertainty is comfort, collect comfort feedback. If it is delivery reliability, track promised versus actual dates. If it is content resonance, study retention and meaningful responses rather than every available metric.

**Exercise:** Finish this sentence: “I will know this change is working when ______.” Then decide when you will check.

7. Something New Today — Satisficing

Herbert Simon introduced the idea of **satisficing** to describe how real people make decisions under limits.

In a perfectly rational fantasy, you could list every option, know every consequence, compare everything accurately, and choose the maximum. Real life does not work like that.

Satisficing means establishing an acceptable threshold and choosing an option that meets it rather than searching indefinitely for an unknowable maximum.

This is not carelessness. The quality of satisficing depends on the quality of the threshold.

For a dining chair, your threshold might include comfort, structural stability, target cost, delivery time, material compatibility, and visual fit. Once an option clears the important criteria, endless searching may create less value than moving forward.

The idea is especially useful in an AI age because generating alternatives has become almost frictionless. More options do not automatically create better judgment.

**Today's experiment:** Before searching, define what “good enough to choose” means. Notice whether the search becomes shorter and more confident.

Design Lesson of the Day — Progressive Disclosure

Progressive disclosure means showing people the information or controls they need now while keeping secondary complexity available for later.

It is common in digital interfaces, but the principle applies beyond screens.

A client proposal does not need every technical detail on the first page. The first layer can communicate package, major choices, price, and next step. Detailed specifications can appear where they become relevant.

The benefit is not simply visual cleanliness. Progressive disclosure protects decision quality by preventing secondary information from competing with the primary task.

The danger is hiding something people genuinely need to decide. Good disclosure delays complexity; it does not conceal consequences.

**Mini exercise:** Look at one document or interface you created. Identify information that is important—but not important *yet*. Could it move one layer deeper?

Furniture Lesson of the Day — Shadow Gaps Need Construction Logic

A shadow gap can make cabinetry, wall panels, consoles, and built-ins feel precise because it separates surfaces with a controlled dark line.

But the visual effect only works when construction can maintain the gap.

If a nominal 5 mm reveal varies from 3 mm to 8 mm, the detail emphasizes error instead of hiding it. Walls, floors, panel thickness, edge banding, hardware adjustment, and installation tolerance all affect the result.

Design the reveal together with the fixing and adjustment strategy. Ask where the installer can absorb variation. Is there a scribe, adjustable bracket, filler, or recessed backing? Also specify what sits behind the gap; a beautiful black reveal in a render can become an unfinished pale wall line on site.

**Factory/site question:** What physical detail guarantees that this shadow line stays visually consistent after real installation tolerances appear?

Workplace Politics — Distinguish Influence From Authority

You will often be responsible for outcomes you do not have formal authority to command.

A project manager may need production, purchasing, design, construction, suppliers, and clients to move together while none report directly to them.

Trying to imitate authority you do not possess creates resistance. Use influence instead.

Make the objective clear. Show dependencies. Reduce the effort required from others. Ask for specific commitments. Give context about why their part matters. Follow up reliably. Escalate only when the dependency genuinely requires authority.

Instead of “I need this today,” try: “The cutting list is blocked until this measurement is confirmed. If we have it by 2 p.m., production can keep tomorrow's slot. Can you confirm whether that is realistic?”

**Rule:** When you lack authority, improve clarity, credibility, reciprocity, and follow-through before increasing pressure.

Key Ideas to Remember

The gap between what exists and what you prefer can become frustration or design material.

Translate judgments into observable conditions. Define a preferred next state instead of demanding an ideal future. Look for small upstream levers. Prototype ideas before defending them. Professional judgment includes deciding what will deliberately remain unimproved for now.

Build feedback close to the change. Satisficing is not mediocrity; it is choosing against a thoughtful threshold when exhaustive optimization is impossible. Progressive disclosure reveals complexity when it becomes relevant. Shadow gaps require a tolerance and installation strategy. Influence is different from authority; clear dependencies and reliable follow-through can move work even when you cannot command people.

Figure of the Day — Herbert A. Simon

Herbert A. Simon worked across economics, psychology, computer science, organization theory, artificial intelligence, and design. He was interested in how humans and organizations make decisions when information, time, and computational ability are limited.

In *The Sciences of the Artificial*, Simon wrote:

“Everyone designs who devises courses of action aimed at changing existing situations into preferred ones.”

That definition makes design much larger than styling.

A production coordinator redesigning a handoff is designing. A manager changing how decisions are documented is designing. A person restructuring a morning so meaningful work happens before messages is designing. A furniture designer changing a joint so installation becomes more reliable is designing.

The quote connects directly to today's chapter because it places agency at the center of design: observe the existing situation, imagine a preferred one, and devise a course of action between them.

A better future becomes design when it gains a path.

Tomorrow — Change One Condition

Tomorrow, notice one thing that irritates you more than once.

Do not complain about it twice.

Describe the current condition without judgment. Write the preferred condition. Then ask: What is the smallest upstream change that would make the better behavior easier to repeat?

Make that change if you can. If you cannot, create the clearest next action toward it.

Do not redesign your entire life in one evening. Change one condition. Then watch what the condition changes in return.

Keep one question with you:

**What small piece of the future can I make easier to happen?**