FIELD GUIDE / PEOPLE ARE COMPLICATED

A practical guide to the delicate machinery of being a person

USER
MANUAL.

SAHIL TAYAL

For colleagues, collaborators, co-conspirators and anyone who has ever said, “Quick question,” and accidentally started a two-hour conversation. A field guide you can actually use.

IMPORTANT NOTICE

This manual contains jokes, metaphors and [FILL IN] fields. It is not a verified psychological assessment. Personal specifications are deliberately left for Sahil to approve.

START HERE / THE 30-SECOND EDITION

People are not
puzzles to solve.

A user manual can make working together easier. It cannot replace paying attention to the actual person. Here's what this entire project is trying to say.

01 / ASK

Check the story.

We hear one sentence and invent the rest. A curious question is usually more useful than a confident guess.

“Can I check what you meant?”
02 / NAME

Make needs visible.

“Whatever works” sounds generous until nobody knows what works. Say what would help, without demanding it.

“Here's what makes this easier for me.”
03 / REVISE

Allow updates.

Humans aren't shipped with permanent settings. Good instructions leave space for changing minds and circumstances.

“That used to fit. It doesn't now.”
FIG. 01 / EXPLODED VIEW (FIGURATIVELY)

A look under
the bonnet.

For conceptual orientation only. Do not attempt to locate the humour module with a screwdriver.

ST—001 / SYSTEM MAPNOT TO SCALE
Illustrated schematic of a fictional human collaboration machine A central illustrated machine with labelled curiosity engine on the left, idea overflow valve upper right, and humour module lower right. These are metaphors, not anatomical claims. 01 / COMPONENTCURIOSITYENGINE02 / RELEASEIDEA OVERFLOWVALVE03 / COREHUMOURMODULEALL LABELS ARE METAPHORICAL
FIGURE 01: FICTIONAL INTERNALSHANDLE WITH CONTEXT ↗
01

Curiosity engine

A useful label for asking the second question—the one hiding behind the first.

02

Idea overflow valve

A reminder to choose which thought gets built, and which gets a parking space.

03

Humour module

A joke can open a door. It should not quietly replace a serious answer.

OFFICIAL-LOOKING / NOT OFFICIAL

Operating
instructions.

Seven sections. Zero supernatural claims. The safest setting remains “ask the actual person.”

SECTION01OF 07

Product Overview

ST / INTRO

One human. Multiple tabs open. No two units exactly alike.

This is a guide to working with someone, not a shortcut to knowing them. It exists to reduce avoidable guesswork: the kind that turns “we should collaborate” into six meetings about what “collaborate” means.

OWNER TO COMPLETE

In one sentence, what I actually do: [FILL IN]

What I want collaborators to understand first: [FILL IN]

SECTION02OF 07

Best Operating Conditions

ST / ENV

Please consult the climate-control panel before declaring something “urgent.”

All people have conditions that make thought easier and conditions that make it feel like filing paperwork underwater. This section is a place to describe preferences, not to demand perfect circumstances.

SETTINGS REQUIRING OWNER CALIBRATION

My ideal working rhythm: [FILL IN]

Meetings / messages / quiet time: [FILL IN]

What helps me reset: [FILL IN]

SECTION03OF 07

Inputs That Work

ST / INPUT

Garbage in, interpretive dance out.

For any collaboration, a decent brief beats a mysterious “thoughts?” Try a real question, relevant context, the decision you need, and whether this is a sketch or a finished sculpture. None of this guarantees agreement. It does improve the odds of a useful conversation.

PREFERENCES — NOT YET VERIFIED

How I like receiving feedback: [FILL IN]

What makes a collaboration exciting to me: [FILL IN]

One input that does not work: [FILL IN]

SECTION04OF 07

Known Bugs

ST / ERRORS

Not defects. Places where context may be missing.

Potential issues in any ambitious collaboration: too many possible directions, jokes arriving before the footnotes, assumptions doing a little freelancing. These are examples, not claims about Sahil. Real bugs need a real witness and a conversation with the owner.

⚠ EXAMPLE ONLY: IDEA OVERFLOW ≠ PERSONALITY DIAGNOSIS
OWNER-REPORTED BUG LOG

A habit I am actually working on: [FILL IN]

Early signal that we're misaligned: [FILL IN]

What people sometimes misunderstand: [FILL IN]

SECTION05OF 07

Troubleshooting

ST / REPAIR

Before restarting the relationship, check the cables.

General collaboration troubleshooting, not a diagnosis
SymptomTry this first
We seem to disagree.Check whether we mean the same thing by the important words.
There are seventeen good ideas.Choose one testable next step. Give the others a respectable waiting room.
Something landed badly.Describe the impact without pretending to know the intention.
A reply isn't instant.Remember the equipment is a person with an offline life.
OWNER-SPECIFIC FIX

The most useful way to raise a concern with me: [FILL IN]

SECTION06OF 07

Warranty

ST / TERMS

Limited warranty. Unlimited humanity.

No human can promise perpetual availability, frictionless agreement or impeccable responses before coffee. Reasonable repairs may include an apology, a clearer expectation, a second attempt or the perfectly respectable decision not to work together. There is no customer-support queue for basic dignity.

BOUNDARIES / OWNER APPROVAL REQUIRED

What I can reliably commit to: [FILL IN]

A boundary I want respected: [FILL IN]

SECTION07OF 07

Contact

ST / CONNECT

For meaningful enquiries, not unsolicited firmware updates.

The correct contact channel and response expectations should be supplied by the person receiving the message. Until then, please resist the ancient ritual of guessing someone's availability from a green dot.

CONNECTION DETAILS — INTENTIONALLY BLANK

Preferred contact method: [FILL IN]

Good reasons to reach out: [FILL IN]

Expected reply window: [FILL IN]

END OF OPERATING INSTRUCTIONSTHE HUMAN REMAINS MORE INTERESTING THAN THE PAPERWORK.
FIELD KIT / FOUR EVERYDAY MOMENTS

Try a better
opening line.

Good communication isn't a magic sentence. But a more careful first sentence can change what happens next. Pick an awkward little situation.

FIELD NOTE / 01NOT A SCRIPTED PERSONALITY TEST

The mysterious “Thoughts?”

THE EASY TRAP

Send a document with no context and hope the other person can read your mind.

TRY INSTEAD

“Could you look at this idea? I especially need feedback on whether the opening is clear.”

WHY IT CAN HELP

A specific request gives the other person a real job, not a guessing game.

Use the idea, not necessarily the exact words. Tone, trust, culture and context matter. Sometimes the best move is to listen.

AN IMPORTANT EXCEPTION / 001

A manual should never become a cage.

“That's just how I am” isn't a free pass to be unkind. Nor does anyone owe strangers a catalogue of their private life. Share what helps. Keep what is yours. Rewrite the manual when you change.

FREE TOOL / ASSEMBLY REQUIRED

Now, write
your own.

DIY / YOU EDITION

A user manual is a conversation starter, not an excuse to avoid the conversation. Start with just three answers if you like. Print a pocket card, or write the full seven-section edition if that feels useful.

Your draft stays in this browser tab. No accounts, analytics, uploads or automatic saving. Download a text copy if you want to keep it.

SPECIFICATION WORKSHEET01—07
ONLY HAVE TWO MINUTES?

Fill in Overview, Inputs That Work and Boundaries. Those three become a pocket-size introduction below. The others are optional.

Name, nickname or mysterious model number. Your choice.

Need a starting point?

Try completing this sentence, in your own words: “I help people ___ by ___. The thing I care about most is ___.”

Need a starting point?

Try completing this sentence, in your own words: “I do better when there is ___, and struggle when ___.”

Need a starting point?

Try completing this sentence, in your own words: “When giving me feedback, please focus on ___ before ___.”

Need a starting point?

Try completing this sentence, in your own words: “I sometimes ___, especially when ___. You can flag it by ___.”

Need a starting point?

Try completing this sentence, in your own words: “If we get stuck, I prefer ___ rather than ___.”

Need a starting point?

Try completing this sentence, in your own words: “You can count on me for ___. I cannot promise ___.”

Need a starting point?

Try completing this sentence, in your own words: “The best way to reach me is ___ about ___. Please allow ___.”

QUICK EXPORT / OPTIONAL

Your pocket manual.

Three useful sentences are enough to start a conversation. It updates from your answers above; no extra fields, and nothing is saved online.

HUMAN EQUIPMENT DIVISIONPOCKET EDITION / 003

[YOUR NAME HERE]

WHAT TO KNOW
Not yet specified.
WHAT HELPS
Not yet specified.
A COMMITMENT OR BOUNDARY
Not yet specified.

A conversation starter. Not a licence to assume.

Keep it short. Keep it honest. Leave anything private off the card.