04 / FIELD NOTES

A few ideas,
in progress.

Short notes about building independent businesses and the decisions behind the work.

INDEPENDENT BY DESIGN   ↘
01 / THE READING ROOM23 ORIGINAL NOTES / THE READING ROOM

All Field Notes

Technical illustration for The freedom to build for the long run.
FIELD NOTE 001 / THE INDEPENDENT ADVANTAGE

The freedom to build for the long run.

Ownership changes who can require which commitments. Independence creates room to choose without supplying the judgment for the choice.

3 MIN READREAD NOTE ↗
Technical illustration for The little things are the whole thing.
FIELD NOTE 002 / ON CRAFT

The little things are the whole thing.

A missing reference can create work across a business. The first obvious fix may move that work rather than remove it.

2 MIN READREAD NOTE ↗
Technical illustration for What one business can learn from another.
FIELD NOTE 003 / THE COLLECTIVE

What one business can learn from another.

A practice makes more sense when its context travels with it. Different businesses can learn from the same observation and still choose differently.

2 MIN READREAD NOTE ↗
Technical illustration for Staying small on purpose.
FIELD NOTE 004 / ON SCALE

Staying small on purpose.

A small team can keep decisions close to the work or leave everyone waiting for one person. Headcount alone does not describe the difference.

2 MIN READREAD NOTE ↗
Technical illustration for The useful question is not “Can we?”
FIELD NOTE 005 / ON JUDGMENT

The useful question is not “Can we?”

A quick output can leave a longer task unfinished. Its usefulness becomes clearer through the work needed to reach a result someone can use.

3 MIN READREAD NOTE ↗
Technical illustration for The anatomy of a good no.
FIELD NOTE 006 / ON FOCUS

The anatomy of a good no.

A yes creates continuing work. A no leaves someone with an unresolved need. Both belong in an account of the choice.

3 MIN READREAD NOTE ↗
Technical illustration for Design the moment after a failure.
FIELD NOTE 007 / ON RELIABILITY

Design the moment after a failure.

After an interrupted action, a person needs an honest status and a usable next step. Better wording depends on work beneath the screen.

2 MIN READREAD NOTE ↗
Technical illustration for Build for the second visit.
FIELD NOTE 008 / ON PRODUCTS

Build for the second visit.

Returning customers bring knowledge of the old interface. A redesign needs to justify the understanding it asks them to replace.

3 MIN READREAD NOTE ↗
Technical illustration for An argument for patience.
FIELD NOTE 009 / ON TIME

An argument for patience.

Time can reveal something a decision needs. It can also leave the same decision waiting, with its costs carried elsewhere.

3 MIN READREAD NOTE ↗
Technical illustration for The dignity of a working business.
FIELD NOTE 010 / ON BUSINESS

The dignity of a working business.

An owner's contribution can be an intentional investment. It should not be mistaken for proof that the service can sustain itself.

3 MIN READREAD NOTE ↗
Technical illustration for A prototype is a question, not an answer.
FIELD NOTE 011 / ON EXPERIMENTS

A prototype is a question, not an answer.

A successful prototype can leave the central uncertainty untouched. What a test means depends on the question and the help supplied along the way.

3 MIN READREAD NOTE ↗
Technical illustration for The price of effortless.
FIELD NOTE 012 / ON EXPERIENCE

The price of effortless.

A saved preference removes work while carrying an old assumption forward. Simplicity depends on what happens when the assumption no longer fits.

3 MIN READREAD NOTE ↗
Technical illustration for Being early is not the same as being useful.
FIELD NOTE 013 / ON TECHNOLOGY

Being early is not the same as being useful.

An experimental tool can arrive with an unspoken need for supervision. The maker's attention is part of what makes the trial work.

3 MIN READREAD NOTE ↗
Technical illustration for Trust compounds quietly.
FIELD NOTE 014 / ON TRUST

Trust compounds quietly.

A customer can trust a business and still check its records. The more revealing burden is the investigation an incomplete promise leaves them doing.

2 MIN READREAD NOTE ↗
Technical illustration for A portfolio is not a personality.
FIELD NOTE 015 / ON THE COLLECTIVE

A portfolio is not a personality.

Shared standards do not require identical methods. A collective changes the boundaries of a decision when its consequences cross between businesses.

3 MIN READREAD NOTE ↗
Technical illustration for Design for the imperfect day.
FIELD NOTE 016 / ON ACCESSIBILITY

Design for the imperfect day.

An interrupted task can become much larger than it looked in a design review. A comprehensible return gives some of that effort back.

2 MIN READREAD NOTE ↗
Technical illustration for Good constraints make space.
FIELD NOTE 017 / ON CONSTRAINTS

Good constraints make space.

An obligation and the method chosen to meet it can look equally fixed. The difference matters when a useful rule outlives its reason.

2 MIN READREAD NOTE ↗
Technical illustration for The handoff is part of the product.
FIELD NOTE 018 / ON TEAMWORK

The handoff is part of the product.

A document can arrive while responsibility remains unclear. The next person inherits the choices it explains and the questions it leaves behind.

3 MIN READREAD NOTE ↗
Technical illustration for Attention is not the same as care.
FIELD NOTE 019 / ON ATTENTION

Attention is not the same as care.

People can spend more time with a product because it helps or because it gets in the way. The activity alone cannot tell us which.

3 MIN READREAD NOTE ↗
Technical illustration for A more generous kind of ambition.
FIELD NOTE 020 / ON AMBITION

A more generous kind of ambition.

A benefit can be funded by people who never agreed to supply it. That complicates what a business means when it calls an ambition generous.

3 MIN READREAD NOTE ↗
Technical illustration for Clarity is a design decision.
FIELD NOTE 021 / ON LANGUAGE

Clarity is a design decision.

Some sentences are unclear because the business has not chosen an answer. Editing improves the explanation; it cannot settle the policy.

3 MIN READREAD NOTE ↗
Technical illustration for Maintenance is a promise.
FIELD NOTE 022 / ON MAINTENANCE

Maintenance is a promise.

A product's continuing promise needs resources, knowledge and limits. Quiet use does not make those obligations disappear.

3 MIN READREAD NOTE ↗
Technical illustration for Build the thing you can explain.
FIELD NOTE 023 / ON SIMPLICITY

Build the thing you can explain.

Explaining the offer can reveal disagreement about who does what. A clear promise still needs a reason for someone to want it.

2 MIN READREAD NOTE ↗
FIELD NOTE / ABOUT THE NOTES

Thoughts are
unfinished work.

These are working ideas from the FiftySeven perspective.

MEET THE COLLECTIVE ↗
Wireframe diagram
LET’S BUILD / 004

Tell us what
you’re working on.

Get in touch to discuss an idea or project.

57° / OPEN CHANNELLET’S TALK ↗