Turn your expertise into a learning journey

An Edwyn workbook for experts, educators and teams. Use it to plan one useful outcome before building a whole course. Copy the templates into your own document and replace the brackets. No account is required. This downloaded workbook does not submit your answers or contact details to Edwyn; your working copy stays with you.

1. Start with a problem you have helped someone solve

Choose a situation where you can explain your decisions, show your working and recognise common mistakes. A topic such as “marketing” is too broad to test. “Write a campaign brief another person can execute” gives you something observable.

Fill in:

I help [specific people] who struggle with [specific task]. After this journey they can [observable action] using [tools or constraints]. They will show this through [work product and explanation]. This journey does not cover [boundaries].

Use verbs such as build, compare, diagnose, prepare or explain. Replace “understand finance” with a task someone can attempt. Ask a potential learner to describe that task in their own words. If their interpretation differs from yours, revise the promise.

2. Define the learner and starting point

Write for a person in a situation, rather than an age or job title alone.

Make prerequisites testable. “Comfortable with spreadsheets” might mean entering formulas, using cell references and explaining a total. Offer a short starter task so learners can judge their readiness before committing.

3. Design the evidence before the lessons

Describe the final task first. Then include only the learning needed to attempt it.

Given [scenario and inputs], create [deliverable]. Explain [decisions and assumptions]. Test it against [edge cases or changed conditions]. Submit [files, links or written reasoning]. Remove [confidential or personal information].

Choose criteria that a second reviewer could apply. Use three states: Needs another attempt, Meets the task, and Extends the task. The middle state is the agreed target; extension is optional. Define revision opportunities and an expected review window before inviting participants.

4. Build one complete learning loop

Use this reusable unit template. A check reveals reasoning; practice produces work; review examines that work.

Avoid checks that merely repeat a definition from the previous paragraph. Change an input or constraint and ask what the learner would do. Give feedback that points to a decision they can revisit. Completing a lesson records study progress; it does not by itself establish capability.

5. Worked concept: finance for startup founders

Fictional course concept, not a published Edwyn course or financial advice. All business names and figures below are invented for an educational exercise. The task is to practise a method and explain assumptions, not recommend a funding, investment or spending decision.

Expertise: translating operating assumptions into a simple cash view.

Learners: first-time founders who can enter spreadsheet formulas but have not built a cash forecast. Prerequisite task: calculate an opening balance plus receipts minus payments, and explain why invoiced revenue may differ from cash received. If that distinction is unclear, provide a preparatory example.

Outcome: using a supplied fictional dataset, build a three-month cash forecast, model a delayed receipt and explain the assumptions that change the result. Submit a spreadsheet and a short decision memo.

Boundaries: no tax treatment, accounting certification, personalised advice or fundraising recommendations. Use fictional inputs rather than a real company's confidential records.

Learn: walk through one month. Opening cash plus cash receipts minus cash payments gives closing cash. Closing cash becomes the next month's opening balance. Show the mistake of counting an invoice as received cash before its payment date.

Check: a fictional customer receives an invoice in Month 1 and pays in Month 2. In which month does this receipt enter the cash forecast? Answer: Month 2. Explain the payment-timing assumption; changing that timing changes cash even when the invoice amount stays the same.

Practice dataset: Paper Kite Labs begins Month 1 with 30,000 currency units. Expected receipts are 10,000, 12,000 and 14,000. Planned payments are 16,000 each month. Build the base case. Then move 8,000 of Month 2 receipts to Month 3. Keep all other inputs unchanged.

Worked reference: base-case closing balances are 24,000, 20,000 and 18,000. Delayed-receipt balances are 24,000, 12,000 and 18,000. The final balance matches, but the path differs. Ask learners to explain that difference and what information would be needed before drawing a real business conclusion. Do not turn the reference figures into a memorisation check.

Evidence: spreadsheet with visible formulas, separately labelled assumptions, both scenarios, one calculation check and a 200-word memo explaining the timing change and limitations.

Optional extension: add a second clearly labelled scenario and explain which assumptions you changed. Review the method and reasoning rather than rewarding a more optimistic result.

Feedback example: “Your Month 2 balance includes the delayed receipt. Move that receipt to Month 3, then check that it appears once. Update the memo to explain why the temporary balance changes.”

6. Make review dependable

Have two reviewers independently assess the same sample before the pilot. Compare the evidence behind each judgement and rewrite ambiguous criteria. Include a sample that meets the task and one with a realistic error. Ask whether a learner could improve from the feedback without guessing.

Agree who reviews, which expertise they bring, how disagreements are resolved and how revisions are handled. Give reviewers accessible files and enough time. Never promise certification, guaranteed employment or an independently verified credential merely because someone completes your journey.

7. Pilot one loop, then revise

Invite a small group you can support. State the time commitment, materials, review process and what feedback you want. Ask permission before recording sessions or quoting anyone publicly.

Record:

• Where learners hesitate or need an explanation.
• Which wrong answers reveal a missing lesson.
• Whether the task produces the intended evidence.
• How long learning, practice and review actually take.
• Whether reviewers interpret the criteria consistently.

Choose release criteria before the pilot: “[Target] participants can attempt the task without extra instructions; reviewers agree on [criteria]; feedback arrives within [window].” Revise unclear instructions before adding more modules. Keep participant work private unless they explicitly agree to a defined use.

8. Plan an offer you can sustain

Answer these questions before deciding a format or price:

Audience: [Who needs this, and how will they find it?] Format: [Self-paced, live cohort, workshop or team programme?] Support: [What is included, and where does it stop?] Capacity: [Participants × review minutes, plus facilitation and administration.] Access: [Schedule, tools, accessibility and preparation required.] Economics: [Preparation, delivery, review, support and operating costs.] Pricing research: [What alternatives does this audience use? What scope would they pay for? What will you test without promising outcomes?]

Set a participant limit you can serve well. Distinguish a future paid offer from today's beta. Edwyn does not promise creator earnings, platform fees or payout terms in this workbook.

Two more starting points

Marketing: create a campaign brief for a fictional product. Check audience-message fit; practise with a changed budget constraint; review clarity, assumptions, measurable objectives and whether another person could execute the brief. Do not promise sales results.

Business operations: map a fictional customer-onboarding process. Check a handoff failure; practise assigning owners and exceptions; review completeness, dependencies, escalation rules and the reasoning behind improvements.

What you can use today

Edwyn's current learner path is the Java invite-only beta, free during beta. Studio offers coordinated creator beta access for course creation, publishing and evidence review. The finance, marketing and business ideas here are planning examples, not published catalogue offerings. Public paid checkout and creator payouts are not live. Skills and School are in development; talent discovery is future direction.

You can use this workbook independently. To discuss creator beta access, email birajdas.freelancer@gmail.com with your target learner, capability outcome and first practical task. Send only the information you choose to share. An email starts a conversation; it does not enrol you, publish a course or activate payments.