Quality grade: defaultTarget customer range, create a form to use next timeHelp us work on our target audience according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] It is segmented into roles, situations, and purchase occasions, and demand is not determined based on gender or age alone. [Results to be created this time] In this material, create an empty form to separate the structure to be reused from the content that changes every time. Briefly describe the content and standards for writing in each space, and provide an example filled with current data. Don't include one-off proper nouns or fictitious achievements as fixed rules. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] You can use the same form for other cases and make sure that required inputs are not omitted. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.
Quality grade: defaultRetrospective of representative work, summary to pass on to othersPlease help me with the representative work retrospective according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Compare time use and actual results and choose what to delegate, stop, and keep. [Results to be created this time] Create a handover document focusing on the current status, what has already been decided, open questions, next actions, and data location. For the person in charge and the deadline, only write what is provided and leave the undecided ones as is. Leave the necessary context so that people who haven't read the original can take the first step. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure recipients know what to look for, where to look, and what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultHow to Request Recommendations, From Blank Document to First DraftPlease help me work on the recommendation request method according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] We consider the time of confirmation of satisfaction and the burden of the request, and do not hide false reviews or compensation. [Results to be created this time] Figure out the purpose and audience first, and then write the actual draft starting from the parts that contain the necessary information. Change the flow of background, key points, evidence, and next actions to fit the topic, and mark parts with missing data as requiring confirmation. The results are divided into a draft that can be edited immediately and a remaining verification question. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure all the facts and figures in your draft match the input and allow the reader to know what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultGrowth experiment priorities and differences between alternativesHelp us prioritize our growth experiments according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Distinguish between hypothesis, expected impact, verification cost, and measurability. [Results to be created this time] If there are alternatives provided, compare them based on the same criteria. If not, suggest two possible approaches based on the current data. Distinguish between appropriate situations, pros and cons, required data, and what to give up for each approach. Rather than saying that one is unconditionally better, please write down the basis for your choice based on the input conditions. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that the comparison criteria and assumptions are applied equally to all alternatives. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultDesign a demand survey, see the results and revise the next versionHelp us design a demand survey according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Connect sample recruitment, questions, response bias, and analysis plan. [Results to be created this time] Compare the initial goal and actual results and share good choices, stuck points, and lack of evidence. Instead of criticizing the judgment at the time based solely on the results, choose no more than two hypotheses to change. Please suggest indicators to maintain, change, and observe in the next attempt. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure you have concrete data to compare improvements to in the next attempt. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultMinimum product scope, summary to pass on to othersHelp us work on the minimum product scope according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Separate functions to verify key hypotheses from functions to be performed later. [Results to be created this time] Create a handover document focusing on the current status, what has already been decided, open questions, next actions, and data location. For the person in charge and the deadline, only write what is provided and leave the undecided ones as is. Leave the necessary context so that people who haven't read the original can take the first step. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure recipients know what to look for, where to look, and what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultManual service experiment, see the results and fix the next versionHelp with manual service experimentation according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Before automation, determine the value to be provided, operating time, and metrics to be recorded. [Results to be created this time] Compare the initial goal and actual results and share good choices, stuck points, and lack of evidence. Instead of criticizing the judgment at the time based solely on the results, choose no more than two hypotheses to change. Please suggest indicators to maintain, change, and observe in the next attempt. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure you have concrete data to compare improvements to in the next attempt. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultMarket size assumption table, convey only the essentialsHelp us work on the market size assumption table according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Reveals calculation formula, source, scope, and possibility of duplication and does not fill in unconfirmed numbers. [Results to be created this time] Select the key points that readers need to make decisions or take action from long materials and create a short version. Do not replace conditions, exceptions, or evidence to make a stronger claim. First, present a short result and distinguish between conditions that should not be omitted and parts that should be passed on as detailed information. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Check with the original text whether the key meanings, conditions, and figures are the same before and after the abbreviation. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultDesign a demand survey, what to check before completionHelp us design a demand survey according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Connect sample recruitment, questions, response bias, and analysis plan. [Results to be created this time] Extract conditions that can actually be confirmed from the data and create a checklist before submitting and sharing. For each item, please write down what to check, how to check, passing criteria, and what to do if not met. Leave unchecked items as unverified and reduce abstract checks that do not require any action. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each item is written with actual behavior and observable results. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultFrom first sales conversation, blank document to first draftHelp you work on your first sales conversation by aligning it with the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Design the conversation based on identifying the partner's problem, determining suitability, and next action. [Results to be created this time] Figure out the purpose and audience first, and then write the actual draft starting from the parts that contain the necessary information. Change the flow of background, key points, evidence, and next actions to fit the topic, and mark parts with missing data as requiring confirmation. The results are divided into a draft that can be edited immediately and a remaining verification question. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure all the facts and figures in your draft match the input and allow the reader to know what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultAffiliate operation experiment, see the results and fix the next versionPlease help us with the affiliate operation experiment according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Determine the scope of sharing of roles, costs, customer experience, and results for both parties. [Results to be created this time] Compare the initial goal and actual results and share good choices, stuck points, and lack of evidence. Instead of criticizing the judgment at the time based solely on the results, choose no more than two hypotheses to change. Please suggest indicators to maintain, change, and observe in the next attempt. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure you have concrete data to compare improvements to in the next attempt. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt