# The Second Door Plan Worksheet Notice, Build, Test, Improve, Share Version 2.0. voyagersbeyond.com This is the editable copy. Type your answers under each prompt, on the blank lines or anywhere you prefer. Nothing here is sent anywhere. --- To turn one lesson from your experience into something another person can try. Start small. You can complete the first line today. The full process takes real attempts and time to learn from them. ## How to use it 1. Fill this in on the page, print it, or download the PDF or editable copy. Writing by hand is fine. 2. Finish the first sentence today. The rest waits until someone has actually tried your method. 3. Steps 3 and 4 need another person. Leave them blank until the attempt has happened. 4. Use examples you are free to share, and remove details that identify someone else or their work. ## What it is not for - Deciding whether to leave your job. The worksheet produces something you can test, not a decision. - Promising job security, an audience, or income. It cannot do any of those things. - Evaluating your worth or your prospects. It examines one lesson, not you. - Replacing advice from someone who knows your specific situation. *This worksheet is an educational reflection tool. It is not a validated instrument and makes no promise about employment, income, or an audience. Suggestions about how many people to ask are practical defaults, not research findings.* --- ## 1. Notice one repeating problem Pick one problem you have actually helped with, not a skill and not a job title. **People ask me for help when:** __________________________________________________ **One specific example, with private details removed:** __________________________________________________ **Who faces this problem?** __________________________________________________ **What would getting past it look like?** __________________________________________________ > Choose one small situation. "Help teams work better" is too large. "Help a team check approvals and availability before promising a delivery date" is small enough to try. ## 2. Build a small first version Write the questions or steps you use, say when to use them, and add one filled-in example. **Give your page a plain name:** __________________________________________________ **Use this when:** __________________________________________________ **The questions or steps, in order:** __________________________________________________ **One filled-in example:** __________________________________________________ **Do not use this for:** __________________________________________________ > Keep the first version to one page if possible. AI can help shorten the words. Check every suggestion against your experience, and do not upload confidential material. ## 3. Test it on a small, low-risk problem Ask someone: "Would you try this on a small task? I want to find the confusing or missing parts." This step happens away from the worksheet. **Person and task, using a private identifier if needed:** __________________________________________________ **Before the attempt, what result will we look for?** __________________________________________________ **What usually happens, if we know?** __________________________________________________ **Date and version tried:** __________________________________________________ **What did the person actually do?** _(after the attempt)_ __________________________________________________ **Where did they need extra explanation or get stuck?** _(after the attempt)_ __________________________________________________ **What happened at the end?** _(after the attempt)_ __________________________________________________ > Ask: "Which question changed what you did? Which part did not help?" Record actions and results separately from compliments. A small trial shows what happened in that setting. It cannot establish that your method caused every improvement. ## 4. Improve it and try again Change the part that failed, then let someone outside your usual team try the revision where that is practical. **The part I changed:** __________________________________________________ **Why I changed it:** __________________________________________________ **What did they not know that my usual colleagues already know?** _(after the attempt)_ __________________________________________________ **Second attempt, person, task and date:** _(after the attempt)_ __________________________________________________ **What happened this time?** _(after the attempt)_ __________________________________________________ **What else changed that might explain the result?** __________________________________________________ **What I can honestly say so far:** __________________________________________________ **What I still do not know:** __________________________________________________ > A past example or a low-risk practice task is enough. You do not need access to another company. If the method still does not help, simplify it, choose a more specific problem, or set it aside. You do not need to turn every lesson into a product. ## 5. Share what you learned Start with one person or group that has this problem. Public posting is optional. Get permission for anything that identifies another person or their work. **Fill in this outline: "I kept seeing [specific problem]. I tried [first method]. In [small test], [what actually happened]. I changed [one thing] because [reason]. In the next attempt, [result]. This may help [person or situation]. I have not tested it for [limit]. If you try it, tell me [specific question]."** __________________________________________________ **Where I will share:** __________________________________________________ **The question I will ask readers:** __________________________________________________ **What they actually did with it, if anything:** _(after the attempt)_ __________________________________________________ > Keep your own dated copy with the example and the result note. A post can link to a longer article if the extra detail helps. A website is optional. --- ## Optional: what comes next This is not a sixth step and not a second framework. It is somewhere to note the next problem when you want one, and to keep track of what you have tried. Leave anything unfinished blank. **My next problem, or my decision to pause:** __________________________________________________ **Who might need help with it:** __________________________________________________ **The first question or small method I could try:** __________________________________________________ **Where I will keep my example, feedback, revision and result:** __________________________________________________ **One person or group I could share it with:** __________________________________________________ **What they actually did with it, if anything:** _(after the attempt)_ __________________________________________________ **A possible later format: group discussion, article, website, workshop, book or video.** __________________________________________________ **A lesson I used in daily work is now a method called:** __________________________________________________ **An assumption about what would help is now an observed result:** __________________________________________________ **A first version with a missing part is now a change I made:** __________________________________________________ **An experience I had not explained is now an example I can share:** __________________________________________________ **A large worry about the future is now one next action I can choose:** __________________________________________________ **Something I feel more able to do now, if anything:** __________________________________________________ ### Collection log One row per method, filled in as you go. Three useful methods can be worth more than thirteen rushed ones. You do not need a long list before sharing the first one. | Problem | Method | Person or setting tried | Finding or change | Shareable example | Next step | |---|---|---|---|---|---| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | --- ## Worked example *This story is fictional. Its attempts and results explain the process. They are not evidence of real-world effectiveness.* #### Worked example: before you promise a date | Step | What happens | |---|---| | Notice | A brochure was promised for Friday. Artwork approval was missing. A Monday event made the delay matter. | | Build | Maya writes four questions: what is promised, who does the work, when it must arrive, and what happens if it is late. | | Test | A colleague replays the failed delivery using the page. Every field can be filled in without naming the approver. Version 1 misses the same problem. | | Improve | Version 2 asks what must happen first and who must help or approve. An events team tries it and spots another assumption: nobody has confirmed the supplier can meet the date. Version 3 adds that check. | | Share | Maya explains both missing questions, her revisions, and the limits in an article. She invites readers to identify other situations where it fails. | In the second fictional attempt, the supplier cannot deliver on Thursday. The team confirms Friday delivery and Saturday setup before making a promise to the organiser. The observed result is a changed plan with confirmed timing. We have not shown that delivery actually happened. #### Completed version 3: before you promise a date Use when finishing something depends on other people. This page cannot guarantee delivery or replace any required professional review. | Question | Events-team example | |---|---| | What are we promising? | Chairs delivered and room arranged before the organiser needs it. | | What must happen first? | Order approval, supplier delivery, room setup. | | Who must do or approve each part? | Event lead approves. Supplier delivers. Room team sets up. | | Has each person confirmed their part and date? | Event lead: Wednesday approval. Supplier: Friday delivery. Room team: Saturday setup. All confirmed in this fictional example. | | What happens if a date changes? | Tell the organiser and review the plan before making a new promise. | > **Finding and limit.** Naming a person or a date does not establish that they have agreed. This page has only been demonstrated in two invented settings. Your own result note must describe what really happened when you tried your method. --- The Second Door Plan Worksheet v2.0. This worksheet is an educational reflection tool. It is not a validated instrument and makes no promise about employment, income, or an audience. Suggestions about how many people to ask are practical defaults, not research findings. The full worksheet is also on the website: https://voyagersbeyond.com/worksheets/second-door-plan-worksheet