What Creators and Innovators Can Learn from Setting the Table
An independent app developer finally ships the feature users have been requesting for months. Early reviews call the update flawless. Buried in the feedback inbox, though, is a message from a longtime user who says the update broke the one workflow they relied on daily, and that they have emailed twice before without a reply. The developer means to respond but gets pulled into the next sprint, and three weeks pass. Meanwhile, a contractor who rushed the release through a weekend never hears a word of thanks, because the developer is already deep into planning the next feature. The product keeps getting better. The people around it, users and collaborators alike, are quietly learning that being excellent matters more here than being noticed.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Distinguishing a great product from a cared-for user
Creators pour enormous energy into making something excellent, and that instinct is not wrong, but it can crowd out whether the people using the work feel attended to as people. A flawless feature shipped to a user whose support request sat unanswered for weeks does not register as care, no matter how well it was built. Genuine attentiveness means treating the relationship with users as distinct from the quality of the output itself.
A creator assumes that continually improving the product substitutes for actually responding to the people using it.
Answer one piece of user feedback personally each week, even when a template reply would suffice.
Treating collaborators the way you want your work to be received
Independent creators and small studios often depend on freelancers and occasional collaborators who receive none of the recognition the finished work gets. If a creator treats these people as replaceable inputs, that same transactional instinct tends to surface later in how they treat the audience the work is for. Building a culture around a creative practice, even a tiny one, starts with genuinely acknowledging the people who helped make it exist.
A creator credits themselves publicly for a launch while the collaborators who made it possible go unmentioned.
Publicly thank one collaborator by name the next time you ship something they helped with.
Hiring and choosing collaborators for temperament, not just skill
Creative and technical talent is easy to evaluate through a portfolio, but the willingness to communicate honestly, admit a mistake, or check in on a struggling teammate is much harder to see in advance and just as important to a small team's health. Choosing collaborators partly for temperament, not only demonstrated skill, protects a creative practice from the resentment that builds when talented people treat each other carelessly.
A founder picks the most talented available collaborator without any sense of how they treat people under stress.
Before bringing someone onto a project, ask a mutual contact how that person behaves when something goes wrong.
Making attentiveness part of the creative process itself
Creative work has natural momentum toward the next release, and attentiveness to people is easy to treat as a side task squeezed out whenever momentum picks up. Sustaining it means building small, recurring habits into the production process, a standing moment to check in with collaborators, a regular pass through user feedback that is not just about bugs, so care survives the excitement of shipping something new.
The sharpest tension is between creative momentum and relational attentiveness. A creator deep in a sprint toward a launch will prioritize the feature over the personal reply, because the feature is what the whole effort is aimed at. But users and collaborators who feel consistently unacknowledged eventually disengage quietly, taking their goodwill elsewhere, which erodes the very audience the momentum was meant to serve. Protecting small moments of attentiveness even mid-sprint is a bet that the relationship, not just the release, sustains a creative practice over years.
Name one thing, honestly
- Which user or collaborator would say they feel genuinely acknowledged by you right now? - What is one message sitting unanswered that says something true about your current priorities? - Where in your process could a small ritual of attention survive even your busiest launch week?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before bringing someone onto a project, ask a mutual contact how that person behaves when something goes wrong.