The Three Parts

You can complete a form, attend a meeting and receive a proposal without becoming any clearer about the work you want. The administration has advanced. Your decision may not have moved at all.

That is the problem this book addresses. Between an initial expression of interest and a company worth committing to, something more useful has to happen than a sequence of follow-ups. You need an account of what you bring, opportunities you can examine and an arrangement you can imagine living with. You also need permission to discover that an attractive opportunity asks for the wrong contribution.

I want the company to take its shape from the person whose judgement will give it value. That requires more than personalising a welcome message. It means allowing what we learn about the person to change the work, the support and sometimes the business itself.

Three parts, three different decisions

The three parts answer different questions. The first makes experience easier to recognise. The second turns that understanding towards possible work. The third assembles the responsibilities needed to make the chosen work possible.

The first row does not select a business. Someone helping you recognise a pattern in your experience has done useful work even if no opportunity immediately follows. That account must be useful enough to carry elsewhere, revisit later or disagree with now.

The second row makes possibilities inspectable. An appealing description is insufficient. You need enough of the customer offer and the working role to discover what attracts you, what you would change and what you would refuse. The result may be a direction to investigate rather than a decision to start.

The third row changes the obligations around you. Tasks need recipients. Support needs to exist. Your contribution needs boundaries. This is where a possible future begins acquiring the structure of an organisation, with consequences for customers and collaborators as well as for you.

Moving between these rows is therefore more consequential than completing successive screens. Recognition, choice and responsibility require different kinds of work. Compressing them into a single conversion process makes it too easy to treat every favourable reaction as permission to advance.

Why start with the person?

If a business has already been selected, the conversation can start interpreting everything about you through its needs. Relevant experience becomes a reason you should join. Unwanted tasks become things you should learn to tolerate. The possibility stops being a question and becomes the answer looking for your agreement.

Beginning with the person gives us an independent basis for judging that possibility. The business may suit your knowledge while requiring a working life you do not want. It may offer enjoyable work while depending on support nobody can supply. We need somewhere to record those distinctions before enthusiasm erases them.

An idea does not remove this need. Bringing a proposal tells us something about a problem that interests you. It does not tell us which parts you wish to carry, how much responsibility you want or what else your experience might make possible. Those questions remain open for an idea-first arrival.

There is an external precedent for taking exploration seriously. In a published London Business School interview, Herminia Ibarra recommends trying possible directions and considering both their appeal and their economic feasibility.¹ That is useful advice for the approach here. It is not a controlled evaluation of Songbird.

One folder carries the reasons

The folder is the continuous object in this journey. It begins with the personal account. It accumulates possible directions, reactions and learning. If a company takes shape, relevant parts become its founding file.

This continuity matters most when the answer changes. A rejected responsibility belongs beside the possibility that exposed it. A revised preference belongs beside the reason for the revision. An unfinished conversation remains unfinished rather than disappearing when the person is given a new status.

Returning to an earlier part should therefore produce a visible change. It may change the personal account, the next candidate or the support that would be required. Repeating the same pitch with warmer language is not a learning loop.

A correction is useful only when the next version changes.

You should be able to reopen the folder after a break and understand the current decision without reconstructing every meeting. The record needs to preserve why a possibility remained interesting, which role you declined and what information you were waiting for. Continuity is a practical service, not simply a memory feature.

Starting does not decide the ending

There are three legitimate directions throughout: carry a company, contribute expertise to another effort, or leave with a clearer account of yourself. A pause can sit between decisions. None of these outcomes should require pretending that you always wanted to be a founder.

The present evidence also needs a boundary. Existing work refining ideas brought to Songbird is narrower than the complete personal-discovery service described here. It would be wrong to treat that work as proof that the full journey already operates as designed. Prepared company foundations are part of the proposition; their actual readiness must be inspected, as Chapter 3 explains.

The test of this book is consequently practical. Can you see what each part should produce? Can you identify an unresolved question rather than accept an unsupported promise? Can you tell whether a change you requested has reached the design?

That begins with the first account. It must contain more than agreeable words about your potential. It needs to be specific enough that you can recognise it, correct it and use it to examine a possibility.

A flattering description is difficult to use. It can call you experienced, resourceful and good with people while leaving every practical question untouched. Which people? In what situations? What do you notice that changes a decision? Which part of that work would you choose again?

The first account needs to make those distinctions. Its purpose is to help you recognise a contribution that may have been hidden inside a job title, a history of ordinary tasks or the work others quietly relied on you to do. Recognition becomes useful when it is specific.

This is the work of the first part. It deserves attention, but it does not have to become an endless search for a final description of you. The immediate aim is an account good enough to guide exploration and precise enough for experience to correct.

What belongs in the account?

Begin with judgement rather than adjectives. Look for decisions you can explain, differences you have learned to notice and questions other people bring to you. A history of doing something provides a starting point; understanding why you did it provides more useful material.

The basis matters because a neat account can become more confident than its material. A recollection is useful, but it remains a recollection. Someone else's praise is evidence of their experience of you, not proof of every claim that could be built on it. An aspiration deserves space without being mistaken for an established ability.

Wanted activity and unwanted responsibility need separate fields. You may be capable of work you no longer want. You may want to try work you have never done. Neither fact cancels the other. A useful exploration distinguishes willingness, ability and the conditions under which the work might become possible.

Constraints belong in the same account as strengths. Otherwise the attractive description of the person travels forward while the conditions of their life are left behind. A proposed role that depends on availability you do not have is not rescued by how well it suits your experience.

These conditions can change. The account should distinguish a current limit from a permanent preference rather than assume either. If something depends on a later decision, keep that dependency visible. Designing as though it has already been resolved creates a false match.

What does the outside eye add?

Another person can notice that apparently separate experiences involve the same kind of judgement. They can ask why a situation was difficult, what you recognised and what made your response useful. That attention can reveal a pattern you had treated as merely part of the job.

The pattern is a proposal for you to inspect. You should be able to say that it is too broad, true only in certain circumstances or accurate about your ability but wrong about your interest. A good retelling becomes more discriminating after those corrections. It does not defend its original elegance.

Ibarra's qualitative study of consultants and investment bankers adapting to more senior roles describes professional development through observation, attempts and evaluation, with an iterative rather than reliably orderly pattern.² Its setting is narrower than this journey. It offers a reason to keep an account open to experience, not a validated procedure for choosing a founder.

Being open to revision does not mean the account is worthless until everything has been tested. It means its claims carry the right status. Some things are well supported. Others are interpretations. Others are questions worth taking into a real encounter.

The idea has its own place

If you arrive with a business idea, put it in the folder. Then separate the problem you recognise, the solution you propose and the contribution you imagine making. A strong understanding of the problem may survive even if the solution changes. An appealing solution may require a role you do not want.

This separation prevents the first part from becoming a pitch-development session by default. Refining an idea can improve the proposal while telling us little about the person who would carry it. The account must remain wide enough to ask whether another arrangement would use the same knowledge better.

If you arrive without an idea, begin with the same fields. You do not need to invent a pitch to qualify for a conversation. Experience may suggest several directions or none that presently merits a business. Both findings can be useful. Personal worth and commercial opportunity are different questions.

When is the account ready to travel?

Take a claim in the account and attach the incident or observation behind it. Identify whether it describes something you have done, something you prefer or something you hope to try. Then ask what would make you qualify it. This simple examination turns a broad description into material a possible role can test.

The account is ready for that purpose when you can recognise a plausible contribution, point to a boundary and name a question that experience could answer. It need not contain a complete life history. It should contain enough to stop the next proposal from treating you as interchangeable.

Keep the earlier version when it changes. The reason for a correction is part of the knowledge being built. If you later consider a similar role, you should not have to discover the same mismatch from scratch.

At the end of this part, you receive the personal account: capability with a basis, wanted work, limits and unresolved questions. You may decide that this is enough for now. If you want to explore further, the next task is to put a possibility beside it. A question about a working role needs more than another description of the person.

The open question in your account needs an encounter with work. You may know that you enjoy a kind of problem without knowing whether you would enjoy the role attached to solving it. A business description can hide that difference. A sample customer output and a working day make it harder to hide.

This is why part two is discovery. Search is useful when you know what to ask for. Here the question itself may still be forming. Offering a concrete possibility helps you distinguish the customer you care about, the task you enjoy and the responsibility you would decline.

The person helping with discovery should learn from those distinctions. Their job is to make the next comparison better. If every response leads back to the same offer, the conversation has stopped discovering anything.

Matching can begin from either side

A personal account can suggest a business worth assembling. The work begins with a contribution and asks what customer problem it could help address. Alternatively, a partly prepared company can suggest a contribution it needs. The work begins with the opportunity and asks who would understand it, want the role and improve its design.

The second direction is an important part of the Songbird proposition. Some work can be done before the right person arrives. A foundation may help someone inspect an opportunity more clearly than an idea expressed in a paragraph. It may also let them enter through a bounded task rather than invent the whole enterprise.

When an opportunity is presented, ask what state it is in. These distinctions are more useful than a single label such as ready:

An idea

A proposed problem, customer and approach. The work is still largely an argument.

A demonstration

Something can be shown: an offer, sample output or simulated workflow. Its behaviour may depend on assumptions or manual preparation.

A working foundation

Specified parts function and can be inspected. Staffing, demand and the rest of the operation may remain unresolved.

A customer-tested operation

There is evidence from actual use. Its scope and relevance still need examination; past use does not settle fit for a new person.

A demonstration is valuable on its own terms. Trouble begins when its appearance is allowed to imply the other states. Ask which parts you can exercise, which are staged and which claims have met customers. An honest answer makes the opportunity easier to evaluate, even when it makes the offer less impressive.

Prepared supply also needs the right operator's interpretation. A modest problem can contain details an outsider misses. That is a reason to take practical knowledge seriously, not a reason to assign every idea a grand value. Welcoming ideas means making room to investigate them. Demand still has to be found.

What should a minimum viable company show?

For discovery, a minimum viable company, or MVC, is a small company-shaped model that makes an offer and its work inspectable. It should show the customer-facing proposition, an example of what a customer would receive, how the work would be performed and the assumptions still supporting the model.

The term does not certify viability. It describes material for examination. A site can tell you what is promised. The sample lets you judge what that promise amounts to. The work map reveals whose judgement, labour and availability would be required. The assumptions identify what the model cannot yet establish.

Keep the original version beside the version shaped around the person. If the original vanishes, it becomes difficult to tell whether the proposed fit changed anything important.

Start with the customer need because fitting cannot be achieved merely by deleting inconvenient work. If removing a task breaks the customer promise, either someone else must carry it or the promise must change. The fitted version then needs its own examination.

Read your role and the surrounding work together. A smaller contribution may be possible because another person accepts operational responsibility. It may also be a fiction created by writing software beside tasks nobody has tested. The comparison should expose the difference.

The uncertainty row prevents a pleasant redesign from inheriting evidence it has not earned. If the customer, offer or delivery changes, evidence for the original may no longer apply. Personal fit can improve while commercial uncertainty increases.

A company can be attractive while its proposed job is wrong for you.

How does a reaction change the folder?

Record attraction and objection separately. A broad yes or no discards information. It matters whether the objection concerns the customer problem, an activity, ongoing responsibility, pace or the absence of support.

1. Name the precise reaction. Locate the part of the offer or day that produced it. Keep enthusiasm for one area from overruling refusal of another.
2. Revise the personal account. Add the newly discovered preference or condition, with its reason. If the reaction contradicts an earlier claim, retain both until the difference is understood.
3. Change the candidate. Alter the role, offer or supporting arrangement. State what changed; an assurance of flexibility is insufficient.
4. Choose a further encounter. Decide what would help you judge the revised possibility. It may be a sample task, a customer conversation, learning or a decision to stop.

These moves are connected. Recording a preference without changing the candidate turns the folder into a diary. Changing the candidate without revising the account leaves the next suggestion vulnerable to the same mistake. The information needs to travel both ways.

There is no research warrant for promising that tailoring always works. In the institutional abstract of their field study, Kooij and colleagues report mixed effects from a job-crafting intervention, including no increase in crafting towards interests.³ The study concerns jobs, not whole companies. Its useful warning here is against treating a fitting process as a universal solution.

For Songbird, the corresponding obligation is to let evidence change the destination. The discovery service should be useful when the person declines an available opportunity. A commercial incentive to keep them moving must not turn an unresolved objection into an obstacle to overcome.

The outputs of this part are the comparison, the corrected account and a next-test decision. You can choose neither version. You can also remain interested while being unable to assess part of the work. That last state deserves a better response than more persuasion: it may need a well-chosen explanation or a smaller way in.

An unfinished judgement can mean several things. You may lack information. You may need to try the work. You may understand it perfectly and have no room for it in your life. You may simply not want it.

Those conditions deserve different responses. Learning can resolve a knowledge gap. A bounded task can expose what a description cannot. A change of pace can accommodate a real constraint. None of them should be used to talk somebody out of an informed refusal.

Education belongs in this journey as a way in and a way back. Someone can arrive to understand business, leave with useful knowledge and return when a possibility becomes interesting. They do not have to declare an intention to found a company before learning is worth providing.

Give learning a job

Begin with the decision that is stuck. What can the person not yet explain, compare or judge? Choose material that addresses that question, then give the understanding somewhere to be used. The sequence is simple, but each part needs to do real work.

Naming the question prevents the learning from expanding to fill every gap in business knowledge. Choosing a resource is an act of judgement: relevance, difficulty and timing matter. Applying it reveals whether it was understood. Explaining the resulting choice reveals whether the person can own the reasoning rather than repeat the language.

The final revision closes the loop. If the material changes an assumption, a question or an intended action, put that change into the folder. If it changes nothing, examine why. Perhaps the resource was wrong, the explanation was incomplete or the original uncertainty was about willingness rather than knowledge.

A carefully selected existing article may be more helpful than a freshly generated manual. Generation can produce an explanation quickly; it does not establish that the explanation is accurate, appropriately demanding or needed now. Curation asks what deserves this person's attention at this point.

Brevity also has limits. The OECD's 2025 adult-learning report identifies work, family and cost barriers, while warning that heavy reliance on very short formats may restrict deeper reskilling.⁴ Sometimes the right response is a short explanation. Sometimes it is sustained learning and a slower decision. Respecting pace means allowing both.

A mini MBA made of working documents

The Songbird mini MBA idea centres on seven documents that the participant must understand and make their own. The point is to turn business knowledge into something usable. A pack that looks complete but cannot be explained has not achieved that.

The following is a proposed arrangement for this book, not a verified list of established syllabus titles. It shows how the seven-document idea could serve the current decision.

These documents should agree with one another. The offer cannot promise work that the delivery document omits. The economics cannot assume support that the responsibilities document leaves unassigned. Your contribution cannot be central in the personal account and absent from the ordinary working day.

Finding a discrepancy is useful learning. Work through it until the participant can explain whether the promise, delivery or role needs changing. That is a more meaningful sign of understanding than recognition of business terminology.

Making the documents your own means being able to question and amend them. It does not mean receiving an impressive file and being expected to trust it. The material should retain the assumptions you are still investigating, so uncertainty is available for action rather than hidden beneath finished formatting.

Learn beside people facing the same difficulty

A small cohort can be assembled around a live question. Its purpose is to compare attempts and interpretations. People need enough common ground for another person's difficulty to illuminate their own; they need not share an occupation or a business idea.

Someone must give the session a useful shape: state the question, examine what each participant tried, identify what remains unclear and decide what each will change. Participation should not require exposing a private folder. People can choose a small piece of working material to discuss.

The value is in what happens after the comparison. A revised question or a clearer limit belongs back in each person's documents. A pleasant discussion with no consequence may be welcome, but it has not yet done the learning work proposed here.

A bounded role can be the classroom

Prepared foundations create another entry route. After inspecting what exists, a person may adopt a limited role in the work. They might investigate a problem, review a sample or join early customer conversations. Accepting that task need not mean accepting operational leadership.

Learning through customer contact has a concrete external analogue: NSF describes customer discovery as part of its practical I-Corps entrepreneurship programme.⁵ The setting is deep-technology commercialisation. The relevant feature here is the method, not a claim that its outcomes will transfer.

The task makes scope concrete. Authority prevents an exploratory contribution from silently becoming permission to promise a service. Accepted support prevents the participant from inheriting everything that was left out of their role description. Review turns the attempt into learning. An explicit ending keeps a small agreement from becoming an indefinite obligation.

A wider role may become attractive after experience. It may not. Someone who understands the customer deeply can help found the company without wanting to be its chief executive. Direction of the domain contribution and management of the operation can belong to different people, provided the arrangement actually supplies both.

Readiness therefore needs an object. Ready for a conversation, ready for a trial and ready to run an operation are different claims. Experience should inform a new choice rather than trigger automatic promotion.

The small role gives the person a manageable place to begin. It also reveals the work outside that place. The next question is unavoidable: if the participant is not doing that work, who is?

The work left outside your role does not disappear. If a customer still needs it, the company must arrange for it to happen. A smaller role becomes credible when the surrounding obligations have real recipients.

This is the practical meaning of company morphing: changing the business arrangement around the contribution a person wants to make. The offer may narrow. Delivery may change. Another person may accept operating responsibility. Software may prepare material that previously required manual effort. The resulting working day should differ because the design has changed.

A personalised name on an unchanged business is not enough. Nor is a promise that the awkward parts will somehow be automated. The person should be able to see which work has moved, where it has moved and what remains theirs.

Fit is constrained by the customer promise

There are limits to what can be rearranged. A customer may need a response at a time the proposed team cannot provide. The participant's preferred activity may supply only part of the value. A supporting role may require resources the business cannot sustain.

Those limits can lead to a smaller offer, a different arrangement or a decision not to proceed. They should be encountered while the company is still easy to change. Fitting the person does not authorise ignoring what the customer needs.

The surrounding organisation matters in work-design research too. Parker, Tims and Sonnentag propose that work characteristics can enable or constrain attempts to reshape a job, while those attempts can in turn alter the work.⁶ This is a conceptual account drawing together research, not a new experiment proving company morphing. It helps locate the question in the whole arrangement rather than in personal motivation alone.

Draw the responsibility picture

A useful picture has three areas. It should be short enough to inspect in conversation and concrete enough to expose missing work.

The first area protects the contribution from becoming a vague founder role. It names what the company needs from you. It also lets you assess whether that is still the work you chose during discovery.

The second area is where many attractive proposals become weak. A capability is not an accepted task. Someone may know how to do the work and have no availability for it. A tool may produce an output without anyone being responsible for checking or using it. Write down the recipient, the expected result and the route for an exception.

Delegation needs an address: somebody has to receive the work.

The third area gives uncertainty an honest place. It should not become storage for inconvenient duties. Each open item needs a consequence: either the trial is limited so the obligation does not arise, or the relevant activity waits until the item is resolved. An empty promise of later support cannot carry current customers.

Agents can organise information, prepare drafts and execute agreed tasks. Their contribution still needs boundaries: suitable inputs, an expected output, checks and a route back when the work cannot be completed within scope. The human contribution includes setting priorities, judging consequential claims and authorising commitments. The details of the technology matter less to this decision than the question of who will notice when it is wrong.

People can supply capability that the participant does not have. An operational leader can coordinate the business. A specialist can examine a difficult question. A domain advocate can help interpret a field or make an introduction. These are distinct contributions; a respected introduction does not certify delivery competence or establish demand.

Adding support should increase the participant's ability to exercise useful judgement. If it instead creates a queue of decisions they cannot understand or an obligation to monitor everything constantly, the proposed relief needs another look.

Read an ordinary day against the picture

The responsibility picture describes the arrangement. A day-in-the-life reveals how it might feel to inhabit it. Use both before asking someone to commit.

1. Trace the ordinary work. Start with what arrives, follow what the participant does and identify where their contribution ends. Check that the expected output has a recipient.
2. Add an interruption. Identify who decides whether a new request changes the day's priorities. A bounded role cannot depend on accepting every interruption.
3. Add an exception. Follow something the normal process cannot handle. Find the person authorised to decide, amend the promise or stop the work.
4. Remove an assumed person. Examine absence. Either another accepted arrangement exists or the scope and timing must change.
5. Close the day. Identify what remains open, who owns it and what evidence shows that completed work is actually complete.

For every action in that account, point to its place in the picture. Work that appears in the day but nowhere in the responsibilities is a design gap. Work that repeatedly returns to the participant despite being assigned elsewhere is a support gap.

Do not make the day attractive by omitting these moments. A person should be able to decline it. The plumber and nurse illustrations that follow will use ordinary work and awkward requests to expose the boundaries.

The human champion has to choose

For the pathway described here, a human champion is a release condition. Someone must understand and accept the contribution that gives the company direction, care whether it produces useful work and be willing to make the judgements that remain.

The champion need not also be the operational leader. That distinction makes a company possible for someone whose domain knowledge is strong and whose appetite for management is limited. It does not remove the need for management where management is essential.

Before a live trial, the champion should be able to explain the customer promise, their role, the support that has been accepted and the circumstances in which work should stop. Enthusiasm without that understanding is insufficient. The gate protects the person from accepting an imaginary role and the customer from an unowned promise.

Passing this check establishes readiness for the agreed trial. It does not certify a successful business. Commercial demand, sustainable delivery and continuing personal fit still need evidence.

The folder becomes a founding file

The founding file carries forward the relevant reasoning: the corrected personal account, original and fitted possibilities, lessons from attempted work, accepted responsibilities and the next test. It records why this company has this shape.

That is a continuation, not a handover to a new process that forgets the person. If later growth reintroduces a rejected responsibility, the founding file should make the change visible. The role can be reconsidered, but it should not drift without a decision.

The output of part three is now inspectable: a proposed company, an accepted contribution, real supporting arrangements, open items with consequences and a test that can change the plan. To see whether those pieces hold together, we need to open a populated folder. We will start with a person who already has an idea.

The first item in the plumber's folder is a business proposal: an online service that helps households book plumbing work. He has noticed how difficult it can be for a household to explain what it needs before a professional visit. He imagines a better initial conversation leading to a better booking.

The proposal contains useful knowledge and several unexamined choices. Helping someone describe a problem is one activity. Finding an available tradesperson is another. Managing the expectations created by a booking is another again. The idea has bundled them together before the plumber has chosen which he wants to carry.

Part one: recognise the contribution

The first conversation stays with his experience. In an illustrative recollection, a householder gives him an unclear account of some non-urgent maintenance work. He separates what the person has actually noticed from what they think caused it, asks what they are trying to arrange and makes the next professional conversation easier to prepare for.

Nothing in that recollection establishes a business. It does suggest a contribution worth examining: translating between everyday descriptions and useful practical information. The account should record that contribution without inflating it into an ability to diagnose every problem remotely.

The broad phrase in the wanted-work row is deliberately unfinished. It records his first account, not the answer the process is supposed to produce. The unwanted-work row already places a constraint on the booking idea. Discovery must take that constraint seriously.

He leaves this part with the personal account, including the idea as one piece of material. He can recognise a contribution without accepting the business originally attached to it. The next part has a clear job: expose the work hidden inside the proposal.

Part two: compare the actual offers

The original MVC presents a household booking service. Its demonstration includes a draft site, a sample booking confirmation and a work map showing how an enquiry becomes an arranged visit. Reading the map makes dispatch and expectation management visible.

A fitted version changes the offer. It helps households prepare a clear description of non-urgent work for their own conversation with a suitable professional. The sample output is a preparation sheet. It does not promise to diagnose the issue, select a contractor or arrange a visit.

The first row changes substantially. A person who wants someone to attend may not value preparation separately. The fitted version could be a better personal fit and a weaker business. That uncertainty has to remain visible; we cannot claim the original demand transfers simply because both offers concern plumbing.

The work row also changes. In the original, a failed arrangement would tend to pull the plumber into coordination. In the fitted version, his central contribution is the quality of the communication material. Supporting work remains, but it is different work and needs a different arrangement.

The sheet gives the plumber something to judge. Does it encourage observation or invite speculation? Does it preserve uncertainty or turn an incomplete account into a confident-sounding conclusion? Does its language imply a service the company has not agreed to supply?

He can correct these features without pretending to operate the business. The correction itself reveals the kind of judgement the company would depend on. It also tests whether reviewing such material is work he would choose repeatedly.

The reaction rewrites part one

Looking at the original work map, the plumber rejects responsibility for managing providers and handling a continuous stream of booking changes. Looking at the preparation sheet, he remains interested in helping people explain what they need. The process has separated two activities previously hidden inside customer-facing work.

The revision is stored beside the comparison that produced it. The fitted company now has to respect it. A later suggestion cannot quietly restore dispatch responsibility merely because a customer would find that convenient.

The output of part two is therefore more than the fitted MVC. It includes both versions, the changed personal account and a next-test note. That note separates whether households value preparation from whether the plumber enjoys producing and reviewing it.

Give the test a decision to inform

A bounded next task could begin with fictional samples. The plumber reviews the prompts and explains his corrections. A collaborator checks whether those explanations can be turned into a repeatable preparation process without losing the uncertainty he wants preserved.

The next customer encounter would have a different purpose. With an appropriate participant's agreement, the team could discuss a recent non-urgent attempt to arrange work and examine what information was difficult to communicate. Only after understanding that experience would they show the sample and ask what it adds, if anything.

This conversation would make no promise to deliver a booking or solve a live problem. An agreed coordinator would handle arrangements and record the limits of the encounter. The plumber's task would be to listen, interpret the practical language and identify which assumptions the account supports or challenges.

Camuffo and colleagues' replicated entrepreneurship experiments found that teaching explicit scientific decision methods affected idea termination and pivoting.⁷ That supports taking a disconfirming result seriously. It does not tell us what this proposed test would find.

A favourable reaction would still need interpretation. Politeness towards a clear document is not evidence that someone would use the service. Equally, a useful customer encounter does not establish that the plumber wants to build a company around it. The next decision must read both accounts.

Part three: rehearse the arrangement

Suppose the revised direction remains worth examining. The following responsibility picture is a proposal for discussion. Its supporting roles are assumed for this illustration and would need actual acceptance before any live work depended on them.

Now rehearse an ordinary day using that picture. The plumber begins with prepared sample material. He checks the parts where judgement matters: whether the question is clear, whether a draft has implied a cause and whether the customer would understand what the sheet does not do. He returns a correction with its reason so the builder can change the prompt rather than repair only that example.

He then joins the agreed exploratory conversation. The coordinator has explained its purpose. The plumber listens for the gap between the household's intended meaning and the draft's interpretation. Afterwards, he reviews the summary and marks where the team has inferred more than the person said.

The coordinator handles the agreed follow-up. The plumber does not need to pursue the administrative thread, but he does need to receive confirmation that the promised follow-up has happened. At the end of the session, he checks the unresolved questions and decides which correction matters next.

This day is a rehearsal, not a report of a functioning service. It makes his proposed contribution tangible: practical review, customer understanding and direction of improvements. It also lets him discover that even this narrower role may contain more review work than he wants.

An impressive demonstration can still contain an impossible working day.

Add an awkward request to the rehearsal: someone contacts the service expecting urgent help. The preparation-only description has not prevented the expectation. Who receives that request? Who recognises that it is outside scope? Who is responsible for the response when the plumber is unavailable?

The unresolved area of the picture now matters. A general statement that the service is non-urgent does not itself assign the work of dealing with unsuitable enquiries. Until the scope, intake and response ownership are adequately arranged, the public service should remain closed. A controlled demonstration can continue without accepting real service requests.

This discovery might require a different interface, an accepted operating role or a decision that the proposed offer is not workable. It should not be used to hand the plumber the continuous availability he already declined.

What is in the founding file?

The proposed founding file contains the first account and its correction, the retained comparison, the fictional preparation sheet, the proposed responsibilities and the test note. It clearly marks customer evidence as pending and supporting roles as unaccepted wherever that is still true.

It also carries the reason behind the fitted shape: the plumber wants his experience to improve communication, while declining provider management. That reason is a design constraint, not background colour. Any future change that affects it requires another decision.

None of those continuations is asserted to have happened. What the illustration demonstrates is the sequence of artefacts and decisions. The original idea gave discovery something concrete to examine; it did not predetermine the business or the person's place in it. The next journey begins without even that idea.

There is no proposal in the nurse's folder. She has not chosen a market, named a service or decided to become a founder. She has experience of work that depends on people passing practical information to one another, and an interest in doing something useful with that experience.

Asking for a business idea at this point would reward her ability to invent a pitch. The more useful task is to discover what she already notices. The plumber supplied a proposed solution before his role was clear. Here both the direction and the role must emerge from other material.

Part one: find the judgement inside the occupation

In this illustration, she describes recognising when a practical request has been passed on without anyone taking responsibility for its completion. A handover can be accurate as a message and still leave the next action uncertain. She is used to asking who will follow it through and what the next person needs to know.

That is more specific than saying she has nursing experience. It suggests attention to coordination, practical consequences and the meaning of information in a workplace. It does not establish that she can sell a service, manage its operations or turn every aspect of her professional knowledge into a company.

The account recognises something without turning it immediately into an offer. A repeated coordination difficulty may matter to an organisation, or it may already have an adequate solution. The person who experiences it may not be the person able to commission help. Those are questions for discovery.

Her interest also remains provisional. Being good at noticing a problem during familiar work differs from choosing to spend a day asking unfamiliar organisations about it. The account gives the next part a question to answer rather than a personality label to confirm.

Part two: examine a prepared possibility

Suppose a foundation has been prepared for exploring non-clinical workflow problems in aged-care organisations. For this example, it includes a draft site, a sample workflow note and a way to organise observations. These are hypothetical demonstration materials, not an operating business with established demand.

The original shape proposes a managed coordination service. It would investigate a difficulty and then take responsibility for an ongoing part of the work. Its working day includes customer conversations, service planning, oversight and follow-up when expectations are not met.

The nurse is drawn to the conversations and the practical interpretation. The ongoing management role is less attractive. A fitted version therefore examines a narrower discovery service: help an organisation describe a coordination difficulty clearly enough to decide what to investigate next.

The fitted offer is smaller, but its value cannot be assumed. An organisation might want a problem solved rather than described. It may regard the note as useful internal work with no reason to obtain it from a new company. Those responses would be evidence about the offer, not a judgement on the nurse's experience.

A tangible sample lets her inspect what her contribution would add. The following note uses fictional process material and no resident information.

The sample deliberately distinguishes an absent fact in the account from an absent process in the organisation. The nurse might recognise that a summary has confused the two. Correcting that inference is a substantive contribution: it stops the team turning incomplete listening into an authoritative recommendation.

She may also find the work interesting but discover that selling and managing a service are being smuggled into the role. The personal account changes in response.

The revision does not rule out ever learning another activity. It records what has been chosen now. The next task should test the listening role rather than treat the broader responsibilities as already accepted.

A pause that preserves the work

Before agreeing to an encounter, she pauses to discuss availability at home. That pause belongs to the design. The question is whether she can give the proposed task proper attention without displacing commitments she wants to keep.

The folder retains the account, the comparison and the unresolved availability decision. It does not translate the pause into a loss of enthusiasm. On return, she should be able to recover the state of the work quickly.

Suppose she returns willing to try a contained activity, while continuing to decline an open-ended role. The next agreement gets smaller accordingly. Her willingness is specific; the service should preserve that specificity.

Learn enough to ask a useful question

Before approaching an organisation, she needs to understand what the conversation is for. It is easy to ask people whether an attractive idea sounds useful. It is harder, and more informative, to ask how a recent situation unfolded and listen for evidence that the proposed offer is unnecessary.

A selected learning resource on customer discovery would be followed by work on the interview purpose. In a small peer session, she could compare question drafts with someone facing the same difficulty. Only the chosen questions need to be shared; the private personal accounts can stay private.

Her first draft might ask whether a clearer coordination process would help. She revises it to ask how the organisation handled a recent non-clinical request, where responsibility moved and how anyone knew it was complete. The revised question allows the organisation to reveal an effective existing process. That possibility is essential to the test.

NSF's I-Corps report describes direct customer discovery within entrepreneurial learning.⁵ The nurse's proposed task borrows the broad method of learning through contact. It makes no claim to reproduce that programme or its results.

She now changes three working documents from the proposed set in Chapter 4. The customer-problem page marks coordination difficulty as an assumption. The responsibility page limits her authority. The next-test page states that an adequate existing process would count against the current offer. She can explain each change in her own words.

A coordinator must accept the arrangements and explain the exploratory purpose. Someone must prepare a draft summary for her to inspect. If those roles are not available, the task needs to shrink or wait. Her expertise does not make every administrative dependency her obligation.

Part three: founder contribution without the CEO assumption

If the direction continues to interest her, the company proposal can put domain understanding at its centre. Her contribution would be listening carefully, identifying practical distinctions and deciding whether the team has understood the situation faithfully. That can be a founding contribution without making her the default operating leader.

The advocate's possible contribution is specific. They could help the team distinguish the people experiencing the difficulty from those able to commission work. They might explain a decision process or make an appropriate introduction. They cannot make the service valuable by association, and their presence cannot substitute for a delivery owner.

Now run a proposed day. The nurse opens the interview plan and checks its purpose. She knows which uncertainty the conversation is meant to address. The coordinator has confirmed the arrangements and the limited scope; she is not arriving under the pretence of representing a fully staffed service.

During the conversation, she follows the organisation's account of a practical request. She asks who received it, what happened next and how completion became visible. If the discussion drifts towards matters outside the agreed scope, she brings it back rather than gathering material the task does not need.

Afterwards, the team prepares a draft note. In the rehearsal, the draft says that nobody owns a handover. She changes it: the conversation did not establish the owner. The revised wording makes the next action an enquiry rather than a recommendation to reorganise the workplace.

She then reviews what was promised at the meeting. An agreed follow-up belongs with the coordinator; a question requiring her judgement belongs with her. The task closes when the note has been checked and the team has decided what, if anything, merits further investigation.

The folder preserves the reason, not just the answer.

Add the awkward moment: the organisation asks who would deliver an ongoing service. The responsibility picture gives the honest answer. That arrangement has not yet been established. The nurse can explain the exploratory stage and take the question back. She cannot turn interest into a promise that somebody else will later have to fulfil.

This moment separates founding contribution from unsupported leadership. If the company depends on an operating role, it needs someone to accept that role. The nurse's willingness to keep investigating is not consent to fill the gap. A company may eventually be arranged around her judgement, but the arrangement must be real before customers rely on it.

The founding file and the next choice

The proposed founding file contains the corrected personal account, the hypothetical foundation's stated readiness, the original and fitted offers, the interview purpose and the responsibility picture. It also retains the pause and resulting limit on scope, because availability helped determine the chosen role.

Evidence from actual customer encounters would be added after they occurred. In this illustration that evidence remains pending. The file must not display an empty evidence section as though the polished surrounding material has answered it.

The next decision has separate branches. If the work is attractive, the need is worth pursuing and operating support can be arranged, she could become the domain founder while another person carries operational leadership. She would still direct priorities in her area and continue learning. Avoiding the CEO role would not make her a spectator.

If she enjoys interpretation but does not want responsibility for a company, she could contribute to another team under a defined agreement. Her knowledge could improve its questions and judgement without requiring her to own the whole direction. The recipient and intended use of that contribution would need to be clear.

If the work proves unappealing or the organisation already solves the problem adequately, the direction can end. She keeps the account, the comparison and what she learned about the role. If current commitments prevent even the smaller activity, she can pause without keeping a company alive in expectation of her eventual consent.

The plumber and nurse now have possible arrangements they can inspect. That does not yet decide how either would relate commercially to a company. Owning, subscribing to or renting something can create very different expectations. Those expectations need the same clarity as the working role.

A role you want and a company you understand still leave a commercial question unanswered: what relationship are you choosing? Owning the business, subscribing to continuing capability and using a company arrangement temporarily are different shapes. The names alone do not tell you who supplies the work or what happens when the relationship ends.

This matters because the fitted role can depend on continuing support. If that support changes, the ordinary day changes with it. Commercial clarity belongs beside the responsibility picture, not in a separate conversation that assumes the picture will remain true.

What does the commercial shape actually include?

Ownership, subscription and rental are possibilities discussed for Songbird companies. They are described here as shapes to make explicit, not currently available packages or settled terms. Each needs an account of what is controlled, what is supplied, what can change and what continues afterwards.

The ownership row separates the business from the services it uses. A person can own an enterprise while depending on outside work. They need to know which dependencies are essential to the role they chose. Otherwise ownership can sound more complete than the working arrangement is.

The subscription row makes continuing provision visible. What result is the continuing capability supposed to produce? Which changes are ordinary maintenance, which require a new discussion and who handles work while that discussion takes place? A useful answer describes the obligations rather than relying on the appeal of ongoing access.

The rental row puts the ending into the beginning. If use is temporary, the participants need to understand what happens to unfinished work and the material created during the arrangement. The company must not depend on an assumed continuation that nobody has chosen.

These are questions to resolve in the particular arrangement. The labels confer no specific rights on their own, and this book does not supply commercial terms. Its requirement is that the person can understand the relationship they are being asked to choose.

Prepared foundations should leave room for fitting

There is a tension inside the idea of an off-the-shelf company. Prepared work can make a possibility easier to inspect and reduce what needs to be assembled from scratch. But if the company comes with a fixed job that the person must absorb, the preparation has chosen the working life in advance.

My proposed resolution is to treat prepared foundations as seeds and make the fitting work explicit. The foundation supplies a starting point. The service of fitting examines and changes the offer, contribution and supporting arrangement. The participant should be able to see what was already present, what was changed for them and what remains unresolved.

Apply it to the plumber. A rental or subscription label cannot make dispatch his job again without a new decision. If the prepared company still requires somebody to coordinate providers, either another accepted arrangement supplies that work or the offer changes. Calling the company fitted does not settle the matter.

Apply it to the nurse. If her proposed role depends on another person leading operations, the commercial arrangement must make that dependency intelligible. What happens if the support ends? Which activities stop? Who closes work already accepted? A reassuring title cannot answer those questions.

Fitting also continues to matter after the first choice. The person may want different work. Customers may reveal that the offer requires a different contribution. A prototype may need more development than was apparent. The arrangement needs a way to discuss change without silently returning all uncertainty to the participant.

A fitted company must stay answerable to the reason it was fitted.

The founding file helps by preserving that reason. It cannot replace explicit agreement about supplied work, control or continuity. Use the file to explain why a proposed change matters, then decide the change rather than assume it.

Three exits are available throughout

Leading a company is one legitimate outcome. Contributing to another person's company is another. Leaving with a clearer account of your experience is another. These choices belong at every part, although the work available to carry forward changes as the folder develops.

A contribution route needs care of its own. Identify what is being offered, to whom, for what use and with what acknowledgement and consent. An exploratory conversation is not permission to absorb someone's knowledge into another business. Keeping contribution distinct from founding should make the agreement clearer, not less important.

Departure should also produce an actual ending. Close outstanding commitments and record what has been learned. Continuing to send proposals after somebody has chosen to stop would undermine the voluntary journey described here. If they choose a pause instead, record the condition under which they want to return; do not assume it.

A decision to end a direction can be informed by evidence. Camuffo and colleagues found increased idea termination following training in a scientific approach to entrepreneurial decisions.⁷ That finding does not make every departure wise. It does challenge a process that treats continuation as the only acceptable evidence of progress.

When a promising arrangement should change

Keep the different reasons separate. Strong personal fit with little evidence of demand calls for customer investigation or a different offer. Strong demand with an unwanted role calls for another role arrangement or another person. A role that works only with unavailable support calls for a narrower scope or a hold.

Automation can create a further mismatch. A task may become easier to produce while checking, exceptions or customer expectations become harder to manage. Read the day again when work moves. Do not judge the change only by the part that became faster.

Prepared supply can also fail to meet the current need. An interesting foundation may be unavailable, incomplete or unsuitable. That is a reason to change the next action, not to lower the standard of fit until something on offer passes. The personal account remains useful even when the available company does not.

Make the next decision small enough to inspect

You can use the following method without deciding to become a founder. Start by locating the question you cannot yet answer. Is it about your contribution, a possible role, customer need or the surrounding work? Bring the actual account, comparison or responsibility picture that contains the uncertainty.

Separate what you know from what you hope. Write the personal-fit assumption, the customer assumption and the support assumption as different entries. If you have no company in view, the customer and support entries can remain open. Do not invent a business simply to complete the note.

Choose an action that could change the relevant entry. A sample task may test enjoyment of work. A conversation may test whether the supposed customer difficulty exists. An explicit discussion with a proposed support provider may reveal whether the arrangement is available. Select the action for the question it can answer.

Before acting, state what would count against the current direction. Also state what the action is not authorised to do. A conversation to learn about a problem should not drift into a service commitment. A prototype review should not be mistaken for accepting the operating role.

After the action, record what happened before explaining it away. Then revise the relevant document. If the outcome changes your understanding of yourself, update the personal account. If it changes the offer, retain the comparison. If it exposes unowned work, change the responsibility picture and the permission to proceed.

Someone who wants to contribute rather than found can use the same note. Their desired result is a useful, bounded contribution with a clear recipient. Someone seeking only a better understanding of their experience can choose a smaller result still. The method does not require either person to progress towards a company they do not want.

Songbird cannot promise that a business will succeed. The commitment worth making is to a journey whose decisions remain answerable to the person, the evidence and the work that must actually be done.

Start the next page with a contribution you want to examine, a responsibility you are declining and a question that needs an encounter with real work. That is enough to give the next conversation a purpose.