Growth Five.

1. Start with a customer, not a storefront
2. Shape an offer and understand the numbers
3. Build a product page that answers questions
4. Run a small launch and learn from it

An online store is a way to present an offer, accept an order and help someone receive what they expected. It is not evidence that anyone needs the product. Before choosing a name or arranging a homepage, describe one customer in one situation. A useful starting sentence is: When this situation happens, this person wants to complete this task, but this obstacle gets in the way. The situation makes your idea specific enough to investigate. Separate the problem from your proposed solution. Someone who struggles to carry lunch and work equipment might want a better bag, a smaller lunch box or a different routine. If every interview question mentions your preferred product, you may miss the real need. Ask about the last time the problem occurred, what the person did, what they tried before and what made the alternative inconvenient. Past behaviour gives you more concrete material than a polite prediction about future purchases. Fictional worked example: Maya is exploring Desktrail, an imagined shop for compact work accessories. Her first idea is a cable pouch for people moving between home and shared desks. Her problem statement says that these workers want to set up quickly, but loose chargers and adapters are difficult to find. In an invented practice interview, a worker describes using an old pencil case. Maya records that description as an observation. She separately records her hypothesis that internal pockets might help. The interview does not establish that the worker would pay for a new pouch. Maya prepares a learning sheet with four columns: observation, interpretation, unanswered question and next check. One observation can support several interpretations. A tangled cable could indicate poor storage, too many cables or an awkward bag. She chooses the cheapest useful check: showing a rough pouch layout and asking the person to arrange their actual items. She does not order stock on the strength of a compliment. Common mistake: describing a customer only as a broad demographic or treating enthusiasm as confirmed demand. A specific situation is more useful than an impressive audience size. A few conversations can reveal questions worth testing, but they do not represent everyone. Useful next step: write one problem statement and arrange a small set of voluntary conversations with relevant people. Explain the purpose, avoid collecting unnecessary personal details and keep exact observations separate from your conclusions. Finish by naming the assumption that could most change your decision to continue.

1. Choose the right task for an assistant
2. Give context, constraints and an output shape
3. Summarise without losing important details
4. Build a repeatable review workflow

Your goal is to choose work where assistance is useful and mistakes can be caught. ChatGPT can help organise supplied notes, develop a first draft or offer alternative explanations. A fluent response is still something to review. It can omit a condition, invent a detail or misunderstand your purpose. Start with a small task whose quality you can judge yourself, rather than asking an unfamiliar tool to make a consequential decision. Use three questions to assess a task. Is the input suitable to share? What would an acceptable result contain? Can I verify that result before anybody relies on it? If one answer is unclear, narrow the task or do it manually. Editing the wording of a fictional meeting agenda is a useful practice exercise. Deciding whether a real customer has a legal entitlement is not an appropriate beginner shortcut. Separate preparation, transformation and approval. Preparation means choosing the facts and removing information you should not provide. Transformation is the requested activity, such as grouping agenda items by topic. Approval means checking the result against the facts and deciding whether to use it. The assistant does not take responsibility for the final message simply because it drafted the wording. Fictional worked example: Maya coordinates a community workshop. Her notes say: 12 seats, beginner level, bring a notebook, room opens at 17:45, session starts at 18:00. She wants a short reminder. This is manageable because the source is small and the output can be checked line by line. She writes down five acceptance criteria before prompting: correct capacity, correct audience, correct item to bring, both times preserved, and no new promises. If a draft invents free parking, she removes it and checks whether other unsupported details appeared. Keep practice data fictional. For real work, follow your organisation's approved tools and data-handling rules; removing a person's name alone may not remove identifying details. Do not assume that a particular plan or setting makes every upload appropriate. Features and availability can change, so this course teaches a review process rather than a specific subscription or button sequence. A common mistake is choosing an enormous task because generation looks fast. A long document can take longer to verify than to write. Your next step is a task card: source material, desired transformation, acceptance criteria and reviewer. Keep the first experiment short enough to compare with the original in a few minutes.

1. Define one audience and one objective
2. Write a message supported by evidence
3. Choose channels with a small experiment
4. Read results without jumping to conclusions

A small campaign becomes easier to plan when it answers two questions: who needs this information, and what observable action matters now? An audience is not merely a list of ages or interests. Describe a situation, a task and an obstacle. Someone may fit your audience but have no need to act today. Your message should help that person judge relevance, not assume that attention means purchase intent. Separate the offer from the objective. The offer is what someone receives, including its scope, price and limitations. The objective is the action you want to observe within a defined period. Awareness, enquiries and purchases are different objectives. Pick one primary objective and keep other measurements as supporting context. A planning target gives you a reference for review; it does not establish what a campaign will achieve. Fictional worked example: Clear Week is an imagined local workshop for people planning their first week of freelance work. Its audience brief says: people with several small client tasks who need a simple way to see competing commitments. The workshop offers a guided planning exercise and a blank weekly worksheet. It does not promise more income or fewer working hours. The campaign objective is to receive eight submitted information requests during a seven-day trial. Eight is a chosen planning target, not a forecast or evidence of demand. Make the counting rule explicit before publishing. For this example, an information request means one completed enquiry form submission. Test entries are excluded; repeat submissions from the same person are noted separately where the available records allow that distinction. A page visit is not an enquiry, and an enquiry is not a booking. Record the observation window and any missing data. Without an earlier comparable campaign, label the baseline unknown instead of inventing an improvement percentage. Write down what you know about the audience and what you still assume. A conversation describing an existing planning problem is evidence of that person's experience. It is not proof that everyone in the audience wants this workshop. Keep personal details out of the working brief when they are unnecessary. Use questions about current behaviour to refine the brief. Common mistake: choosing followers as the main measure when the actual goal is information requests. A larger follower count cannot answer whether people asked about this offer. Next step: complete a one-page audience and objective brief, including a counting rule, time period and one assumption you need to investigate.

1. Give every piece a useful job
2. Structure a clear opening, middle and ending
3. Create with accessibility in mind
4. Publish, reuse and improve responsibly

A useful piece of content answers a recognisable question for a particular person. Starting with a format, such as a post or video, can hide that purpose. Start instead with the audience's situation: what are they trying to do, what do they already know and where do they get stuck? A narrow answer can be more useful than a broad introduction that leaves the reader unsure what to try. Choose one takeaway that fits in a sentence. This is the idea the audience should be able to explain or apply afterwards. Separate it from your publishing goal. Publishing every week describes your activity; helping a beginner identify the next item they need describes a useful audience outcome. You can plan for that outcome without claiming everyone will achieve it or that the content has already helped real people. Fictional worked example: the imagined project Small Desk Notes creates a short guide for someone returning to a crowded home desk. The question is, How can I prepare this space for my next task? Its takeaway is, Keep the materials for one chosen task within reach and give unrelated items a temporary place. The guide is not a promise of better health, higher productivity or a permanently tidy home. It is a modest organising procedure the reader can adapt. Build a six-field brief: audience, question, takeaway, evidence, format and next step. For Small Desk Notes, the format is a short illustrated explanation, and the next step is to arrange one task's materials. Evidence consists of an original staged example showing the sorting process. That example can demonstrate the instructions, but it cannot prove broader performance benefits. Label observations from your own practice as observations, not universal facts. Collect only what the piece needs. Write down which statements require checking, which images you will make yourself and which outside materials would need permission or suitable usage terms. Avoid including private papers in a desk photograph. If another person appears or supplies an example, agree how their contribution may be used before publication. Keep unresolved questions visible rather than filling them with confident guesses. Common mistake: expanding a simple desk guide into advice about scheduling, storage purchases and motivation before teaching its one procedure. The extra subjects compete with the promised answer. Next step: complete the brief and write a short boundary sentence stating what the piece will not cover. Use the brief to judge every planned section: if it does not help answer the chosen question, save it for another piece.

1. Write the promise before choosing colours
2. Build a small, usable visual system
3. Find a voice that makes information clearer
4. Keep the brand consistent across the journey

A brand is the expectation someone builds from repeated experiences with a business. Its name and appearance help people recognise it, but the product, explanation and response to problems determine what that recognition means. Start by deciding what customers should reliably expect. A promise should guide real choices, not simply provide an attractive line for the homepage. Describe the audience by a situation and a need. Then write the useful difference you intend to provide. A working formula is: For this audience in this situation, we offer this product with this specific focus. The difference can be modest. Clear sizing information, a tightly selected range or easy-to-understand instructions can provide direction without claiming the business is the best at everything. Support the difference with evidence or a concrete operational commitment. Fictional worked example: Paperpath is an imagined shop selling paper planning pads for people coordinating small community projects. Its draft promise is, Simple planning pages that keep shared tasks visible. The promise does not say that buying a pad will remove stress or make every project successful. Instead, the fictional product concept includes space for a task, its owner and its next review date. These design choices connect the promise to something a buyer could inspect. The founder, Nia, chooses three attributes: clear, practical and considerate. She translates each into behaviour. Clear means showing a filled-in sample alongside an empty page. Practical means explaining what belongs in each field and what can be left blank. Considerate means avoiding language that shames a person for unfinished tasks. If a proposed advertisement says never miss a deadline again, it fails the promise test because the pad cannot control the team's actions. Test a promise against the whole experience. Can the product support it? Can the description show it? Can support behave consistently when something goes wrong? A useful brand choice also excludes something. Paperpath might avoid a huge catalogue of unrelated decorative goods because maintaining a focused planning range better supports its present purpose. This is a working choice, not a rule that the business can never change. Common mistake: selecting generic adjectives such as premium, innovative and trusted without specifying what anyone would observe. Another is copying a competitor's promise while lacking the same product or capabilities. Useful next step: write one promise, three attributes and one observable behaviour for each attribute. Add one claim you will deliberately avoid. Review the set against a product sample and one difficult support situation before considering names, logos or colours.