u/84tiramisu

[ Removed by Reddit on account of violating the content policy. ]

[ Removed by Reddit on account of violating the content policy. ]

[ Removed by Reddit on account of violating the content policy. ]

I have been preparing for consulting interviews, and I think I am running into a strange problem. The more cases I practice, the more structured I get. At the same time, I sound more mechanical. I can start with the objective, lay out a few buckets, ask for data, do rough math, and close with a recommendation. That part has improved. In mocks, though, I sometimes catch myself forcing a framework before I have really understood the business problem. It feels like I am trying to prove that I know how case interviews work, but not actually thinking through the case.

I have been practicing with case books, ChatGPT, Beyz interview assistant and peer mocks. But I am still struggling with how to make the structure feel natural, especially when the interviewer gives a vague prompt or pushes back on one of my assumptions. How did you move from “using frameworks” to having a clear business conversation?

I am trying to clean up how I track project risks and decisions because right now the process feels too scattered.

Some risks start in Slack. Some come up during stakeholder calls. Some are buried in Jira comments. Some only become obvious after someone says something vague like “we might need to revisit that later.” By the time I write the weekly update, I am usually piecing things together from five different places.

Right now my rough setup is Jira for confirmed work, Notion for decision logs, Slack for quick updates, and a separate doc for risks that are not ready to become tickets yet. For calls with a lot of moving context, I have also been keeping transcripts in the review flow and using Beyz meeting assistant alongside the rest of the stack. The part I am still trying to improve is the middle layer. Some things are too important to leave in Slack, but too early to turn into Jira tickets.

How do you track risks and decisions before they become formal tasks or status report items?