{"id":"exec-week-one-hypothesis-plan-table","audience":"consultants","category":"leadership-work","track":"leadership","level":"advanced","technique":"constraints","title":"Plan week one of an engagement as a hypothesis-driven table","free":false,"task":"Plan the first five working days of the pricing engagement as a markdown table with columns Day, Hypothesis to test, Data or interview, Owner. Exactly 5 rows, Mon to Fri. Each hypothesis is a statement that could be proven wrong. Only use data or interviews that the notes say are available on that day, and do not schedule anything on a day the source is unavailable. Output only the table.","materialLabel":"Engagement notes (attached to your prompt automatically)","material":"Client: Marlow Instruments (fictional). Question: why did average discount rise from 11% to 17% in 12 months?\n\nTeam: Jess (lead), Tomas (analyst).\n\nAvailability\n- Sales transactions export: Monday (Finance delivers by 10 am).\n- CRM opportunity notes: Tuesday onward.\n- Interviews: Head of Sales (Wed or Thu only), two regional managers (Thu only, 30 min each), CFO (Fri only).\n- Competitor price list: Not available.\n- Discount approval log: Wednesday onward.\n\nInitial ideas (not facts)\n- Discounts rose because a new low-priced competitor entered in spring.\n- Discounts rose because approval limits were loosened in April.\n- Discounts concentrated in the last 3 days of each quarter.\n- Larger deals get larger discounts, and deal size grew.\nOwner guide: Tomas runs data; Jess runs interviews.","rules":[{"type":"maxWords","max":190},{"type":"plainText"}],"mistakes":[{"title":"Using unavailable data","why":"The AI schedules the competitor price list.","fix":"Say: \"Only data available that day.\"","checks":["r2"]},{"title":"Scheduling on the wrong day","why":"The AI puts the CFO on Wednesday.","fix":"Say: \"Respect availability: CFO Fri only.\"","checks":["r1"]},{"title":"Questions, not hypotheses","why":"The AI writes 'Why did discounts rise?'.","fix":"Say: \"Each hypothesis is a statement that could be proven wrong.\"","checks":["r1"]},{"title":"Wrong shape","why":"The AI adds columns or rows.","fix":"Say: \"Columns: Day, Hypothesis to test, Data or interview, Owner; five rows.\"","checks":["r0"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for a total word limit and it often lands over it.","fix":"Cap each cell: \"each cell under 14 words.\"","checks":["maxWords"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for a total word limit and it often lands over it.","fix":"Cap each part instead, for example: \"each line under 12 words.\"","checks":["maxWords"]},{"title":"Adding headings and bold","why":"The AI wraps the table in headings, bold goals and notes.","fix":"Say: \"Plain text: only the table, no headings or bold.\"","checks":["plainText"]}],"promptHints":[{"label":"Columns","patterns":["day","hypothesis","data or interview","owner"]},{"label":"Five rows","patterns":["5 rows","five rows","mon.*fri"]},{"label":"Testable","patterns":["statement","proven wrong","testable"]},{"label":"Availability","patterns":["available","availability"]},{"label":"Owner","patterns":["tomas","jess"]}],"hint":"Name the columns, require testable statements, and tell it to respect availability.","rubricLabels":["The output is a markdown table with columns Day, Hypothesis to test, Data or interview and Owner with exactly five rows Monday to Friday","Each hypothesis is a testable statement based on the initial ideas, and each data or interview entry is available that day (transactions Mon, CRM or discount log from Tue/Wed, Head of Sales Wed or Thu, regional managers Thu, CFO Fri)","No row relies on the competitor price list, and owners follow the guide (Tomas for data, Jess for interviews)"]}