Build a spreadsheet with two tabs. Tab one is Monthly Budget with columns for Category, Budgeted, Actual, Variance and Notes. The Variance column should be a formula, not a typed number. Tab two is Summary, pulling totals from tab one by category with a formula.\nAdd a drop-down on Category limited to: Payroll, Software, Marketing, Travel, Other.\nFormat currency columns as currency and highlight any negative variance in red.\nDo not invent figures. Leave Actual blank for me to fill.
Here is an unstructured list of items. Build a spreadsheet that organises it into columns you choose based on what is actually in the data, not a template.\nBefore you build it, tell me which columns you picked and why, and name anything in the list that did not fit so I can decide what to do with it.\nAdd a status drop-down and freeze the header row.
I am going to describe our next quarter out loud. Build a board from it with a timeline across the top, one swimlane per owner, and dated items placed on the timeline.\nWhere I name a dependency, show it. Where I am vague about a date, leave the item off the timeline and put it in a parking area rather than guessing.\nWhen the board is done, list every assumption you made.
The board has notes from our retro. Group them by theme rather than by who wrote them, and name each theme in the words the team used, not in management language.\nFor each theme, draft one action item with a suggested owner based on who raised it.\nFlag any theme where the notes disagree with each other instead of merging them into a single statement.
Looking only at the cluster I have selected, answer this: what is the earliest item here that nothing else depends on?\nExplain which items you checked to reach that answer, and say so plainly if the dependencies on the board are not complete enough to be sure.
I want to certify our definition of active customer in Claude Data.\nFirst, show me every way this metric is currently calculated across the connected tables, including any that disagree.\nThen propose one definition, written as SQL, and list exactly which existing reports would change their numbers if we adopted it.\nDo not certify anything until I confirm.
Build a dashboard answering: how did revenue move last month, and what drove it.\nFor every number shown, include the query that produced it so a reader can check it.\nWhere a change is within normal variation, say so rather than describing it as a trend.\nSet the refresh schedule to daily and tell me what it costs to run at that frequency.
Draft a data story from this dashboard for an audience that does not know our schema.\nLead with the finding, not the methodology. Define every internal term the first time it appears.\nMark any claim that rests on a single query or a small sample so I can decide whether to keep it.\nDo not share it. Leave it for my review.