Think analytically

I'm drafting a precise definition of 'analytical thinking' for mathematicians that clearly separates it from 'intuition' and from 'creativity'. Using The Pyramid Principle and Kahneman's System 1/System 2, write a 3-sentence definition that would survive cross-examination by a skeptical colleague who insists pattern recognition counts as analysis. Then list two short, concrete tests I can use to tell the difference in a colleague's work (not quizzes—work artifacts).

Map 'analytical thinking' for mathematicians across levels 1–5. For each level give 4 observable behaviors (in proofs, seminars, code, or advising) and name one tipping indicator that distinguishes the next level up. Ground the map in the Pyramid Principle and hypothesis-driven solving.

Explain from first principles why 'hypothesis-driven problem solving' works for verifying a mathematical conjecture. Reduce the mechanism to a psychological/epistemic kernel: what cognitive operations are being offloaded or engaged? Cite Thinking, Fast and Slow and The Pyramid Principle to justify each component, and propose one lab-style micro-experiment a department could run to show the mechanism empirically.

Describe a mathematician who 'thinks analytically' but in reality produces weak analysis. Use Hypothesis-driven problem solving and Issue tree diagnostics to list 6 specific tells (observable in seminar notes, proofs, or model writeups) that reveal this anti-pattern. For each tell, give a one-sentence explanation and a realistic micro-intervention I can deliver in a critique session.

Roleplay a real-time review: You're my thesis advisor playing Devil's Advocate. I'm presenting a short analysis of a counterexample where my proof attempt fails. Use Socratic questioning and the Pyramid Principle to push me toward either a fixed proof or an explicit revised conjecture. Ask the next question after I respond and don't soften when I hedge. Start by saying: 'State your top-level claim in one sentence.'

Walk me through a single realistic story (500–700 words) where a math research project failed because of poor analytical thinking. Use Rumelt's diagnosis idea and show the earliest three warning signs tied to concrete artifacts (emails, notebook entries, proof drafts). End with one actionable remediation we could have done in month two to rescue the project.

Explain, using the Issue tree / logic tree method and the Pyramid Principle, how 'analytical thinking' should change when a pure-math problem solver moves from a university lab to (a) a venture-backed ML startup and (b) a large regulatory financial firm. For each context, list three changed priorities, one altered diagnostic question, and one concrete change in daily habit. Be specific to artifacts: grant vs term-sheet vs compliance report.

I wrote this Slack message to a collaborator about a stalled proof: "Can you rework Lemma 3? The current draft is confusing and probably wrong. I don’t have time to fix it." Rewrite it to demonstrate strong analytical thinking using The Pyramid Principle and SBI (Situation-Behavior-Impact): state the top-line conclusion first, group 2–3 evidence points that show the exact error(s), and end with a concrete, testable next-step. Keep it <140 words and keep the math precise (refer to Lemma 3, eqns, or counterexamples).

I’m a US-trained mathematician mentoring a visiting collaborator from a culture where deference to seniority is strong. Using Socratic questioning and the Issue tree framework, explain three ways our analytic practices (proof style, error-calling, paper authorship) typically clash, give a short example dialogue for each (2–3 lines), and give one practical rule to prevent each clash so analysis stays rigorous without causing cultural offense.

Take the 1993 proof retraction of the original Hasse–Minkowski argument (famous failure). Argue exactly how applying an Issue tree / logic tree plus a hypothesis-driven attempt to disconfirm the central lemma could have prevented the error. Produce a short timeline of steps that would have caught the bug, and name the specific tell — a tacit sign in the manuscript or seminar — a practicing mathematician would notice that a book wouldn’t list.

Last Thursday I led a 20-minute methods review with my math group about a stubborn conjecture. I caught myself saying ‘let’s try more data’ twice and avoided naming the key assumption I disagreed with. Coach me as if you’re using the Hypothesis-driven problem solving frame: how should that moment have shaped my words, the exact question I ought to have asked, and a short script (3–4 lines) I can rehearse for next time.

Explain concretely what being analytical (think analytically) looks like for a junior postdoc, a senior researcher, and a lab manager in our math department. Use the Issue tree / logic tree frame: give one small logic tree each role would build for deciding whether to pursue a new proof approach, and list one tacit signal that differentiates junior from senior behavior.

Simulate a 6-turn disagreement between two mathematicians who both think analytically but reach opposite conclusions about abandoning an approach: Person A uses The Pyramid Principle—top-down diagnosis says stop; Person B uses Good Strategy / Bad Strategy—diagnosis shows leverage, so continue. Keep each turn 1–2 sentences, expose the hidden assumptions, and end with a forced tradeoff they must pick.

I'm a research mathematician who prizes rigor and exhaustive proof. Using the Pyramid Principle, Socratic questioning, and the idea of hypothesis-driven problem solving, run a 12-minute simulated internal dialogue where I test whether an obsession with fully formal proofs is harming my productivity and impact. Be concrete: name at least three trade-offs (e.g., publication delay, collaboration friction, missed heuristics), assign rough magnitudes (small/medium/large) to each, and force me to choose which trade-off I'm willing to accept. Don't flatter — if I'm rationalizing, call it out plainly.

I'm interviewing a candidate for a research group; I have 45 minutes and can't ask 'Are you analytical?'. Using hypothesis-driven problem solving and Socratic questioning, design a four-part interview that reveals their analytical ability indirectly. For each part give the prompt I'll say, what specific behaviors or phrases I'll score (3–5 items), and what quick rubric (strong/weak) maps those behaviors to. Keep everything doable within 10–12 minutes per part.

Assess my analytical thinking. Ask me 10 diagnostic questions, one at a time, using Socratic questioning and the SBI analytic feedback variant. After each my short answer, tell me whether my response shows strength, weakness, or mixed evidence and why — be blunt. After all ten, give a candid overall readout and one specific 'next experiment' I can run in my next week to move one weak area to mixed.

Give me a single 5-minute daily practice that will measurably improve my analytical thinking as a working mathematician. Use the Pyramid Principle to explain the mechanism, name one bias from Kahneman it combats, and give a one-week schedule showing exact prompts for each day's 5 minutes.

Play devil’s advocate: argue that rigorous analytical thinking (hypothesis-driven, issue-tree, Pyramid-style) is overrated for pure mathematicians — make the strongest case (5 points) that intuition, pattern-seeking, and long-term exploration matter more. Then rebut each point from the opposite side with a concise analytic counterargument that cites Thinking, Fast and Slow or Good Strategy / Bad Strategy. End with where the truth likely lands (balanced policy for a math department).

Design a 30-minute workshop for graduate students to teach 'think analytically' using Socratic questioning. Include: a 5-minute opener, one 12-minute group exercise with precise prompts and expected outputs, a 8-minute debrief structure (questions to ask), and a one-sentence learning check.

Give me five post-meeting questions I can ask myself to evaluate how well I applied analytical thinking, each tied to a named framework from the dossier (e.g., Pyramid Principle, SBI analytic feedback, Issue tree, Hypothesis-driven, Socratic). Keep each question actionable and give the single best observable sign that answers 'no'.