Quality grade: defaultHow to request a recommendation, organize questions before startingPlease 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] Distinguish between information that can be confirmed based on current data and information gaps that change the outcome. Write down the reasons for each question and the parts that vary depending on the answer, and suggest up to three questions to check first. Once you receive the answer, please update the agreed upon task summary. [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] Please check whether the question already has an answer in existing materials or is simply a question of preference. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.
Quality grade: defaultCustomer problem hypothesis, create a form to use next time as wellHelp us work on customer problem hypotheses 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] Inconvenience, current alternative, frequency of occurrence, and willingness to pay are divided into observation and hypothesis. [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.Copy prompt
Quality grade: defaultOutsourcing request scope, create a form to be used next timePlease help us meet the scope of outsourcing requests 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 output, inspection standards, schedule, data, and scope of revision. [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.Copy prompt
Quality grade: defaultChange business direction, summary to pass on to someone elseHelp us change business direction 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] Divide between assets to keep, hypotheses to discard, and new risks to test. [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: defaultUnit economic calculations, summary to pass on to othersHelp us calculate unit economic feasibility based on 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] Separate sales, variable costs, fixed costs, and customer acquisition costs and adjust their units. [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: defaultOne page business introduction, revised version reflecting feedbackHelp me work on a business introduction 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] Organize customer problems, solution methods, reasons for progress, and requests into one flow. [Results to be created this time] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [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 previously confirmed conditions are preserved and requested feedback is reflected. 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: defaultCompare collaboration partners, organize questions before startingHelp us compare collaboration partners 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] Role, contribution, performance basis, dependability, and fungibility are compared using the same criteria. [Results to be created this time] Distinguish between information that can be confirmed based on current data and information gaps that change the outcome. Write down the reasons for each question and the parts that vary depending on the answer, and suggest up to three questions to check first. Once you receive the answer, please update the agreed upon task summary. [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] Please check whether the question already has an answer in existing materials or is simply a question of preference. 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: defaultConfirmation list before release, leaving only the essentials and delivering themHelp us work out the pre-launch checklist 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] Core flows, support, settlement, documentation, and failure response are inspected in line with the actual scope of provision. [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: defaultScope of outsourcing request, summary to be passed on to othersPlease help us meet the scope of outsourcing requests 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 output, inspection standards, schedule, data, and scope of revision. [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, creating a form to be used again next timeHelp 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] 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.Copy prompt
Quality grade: defaultRecommendation request method, revisions reflecting feedbackPlease 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] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [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 previously confirmed conditions are preserved and requested feedback is reflected. 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: defaultSales follow-up contact, items to check before completionHelp us align our sales follow-up contact efforts 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] It reflects the agreements and unanswered questions from the previous conversation and does not make new promises. [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: defaultOne-page business introduction, pointing out the differences between alternativesHelp me work on a business introduction 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] Organize customer problems, solution methods, reasons for progress, and requests into one flow. [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: defaultCheck out the rate plan composition and differences between alternativesHelp us configure the rate plan 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] Differences in usage and functionality by customer group are linked to billing units. [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: defaultChange business direction, look at the differences between alternativesHelp us change business direction 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] Divide between assets to keep, hypotheses to discard, and new risks to test. [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: defaultCustomer problem hypothesis, things to check before completionHelp us work on customer problem hypotheses 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] Inconvenience, current alternative, frequency of occurrence, and willingness to pay are divided into observation and hypothesis. [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: defaultMarket size assumption table, summary to pass on to othersHelp 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] 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: defaultPrioritize growth experiments, organize questions before startingHelp 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] Distinguish between information that can be confirmed based on current data and information gaps that change the outcome. Write down the reasons for each question and the parts that vary depending on the answer, and suggest up to three questions to check first. Once you receive the answer, please update the agreed upon task summary. [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] Please check whether the question already has an answer in existing materials or is simply a question of preference. 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, revisions based on feedbackHelp 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] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [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 previously confirmed conditions are preserved and requested feedback is reflected. 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: defaultCreate a form for your first sales conversation and future useHelp 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] 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.Copy prompt
Quality grade: defaultComparison of work options and conditional recommendationsYou are a decision-making partner who organizes the criteria and basis for decisions. Please review the issues to be decided {{goal}}, decision materials {{material}}, constraints {{constraints}}, and existing records {{history}}. If the scope of the goal or alternative is ambiguous, first ask up to three questions that will change the comparison results. Match the alternatives to the same period and scope and see if maintaining the status quo is an option. After distinguishing between conditions that must be met and preference standards, select ‘Alternative | Prerequisites | Cost/Time | Expected Benefits | Burden | Please fill out the ‘unconfirmed information’ table. Distinguish between facts and estimates in the data, and leave missing figures in need of confirmation. Weighted scores are only used when I tell you the priorities. Next, organize up to three conditional recommendations to determine which alternative is advantageous under which conditions. Select three pieces of information that are likely to change your current judgment and suggest confirmation methods and roles. At the end, write in one paragraph the scope of what you can decide now and the scope that needs further confirmation. Each comparison is complete when evidence is connected and all required conditions are met. Planning reference: @fish__.bread https://www.threads.com/@fish__.bread/post/DdgpJIhgE6N Create a prompt: PrompthereCopy prompt
Quality grade: defaultCalculate unit economic feasibility, see the results and fix the next versionHelp us calculate unit economic feasibility based on 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] Separate sales, variable costs, fixed costs, and customer acquisition costs and adjust their units. [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: defaultAssuming break-even, look at the results and fix the next versionHelp me work out my break-even assumptions based on 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] It shows the calculation and sensitivity of fixed costs, contribution margin per case, and required sales volume. [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: defaultScope of outsourcing request, review results and fix next versionPlease help us meet the scope of outsourcing requests 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 output, inspection standards, schedule, data, and scope of revision. [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