top of page


Every successful company, every well-run project and every major decision that’s landed well has had at least one good analyst involved.


Not always someone called an analyst. But someone who could see through the noise, ask the right questions and bring clarity to complexity.


So, what really makes a good analyst?


It’s not just PowerBI skills or dashboard mastery. It's a mindset. A mix of curiosity, rigour and storytelling. A good analyst doesn’t just crunch the numbers - they challenge assumptions, test perspectives and help teams make informed decisions.


Here are some of the key skills and attitudes that define the very best:

 

🔍 Attention to Detail


The best analysts spot what others miss. In a sea of data, they notice the inconsistent date format, the odd outlier, or the assumption hidden in plain sight. Attention to detail builds trust and without trust in the data, nothing else matters.

 

🧠 The Willingness to Probe


They ask, “Why does this look like that?” even when the answer might go against the grain. Challenging the status quo isn’t easy, especially when the evidence suggests something inconvenient. But good analysis doesn’t serve comfort. It serves truth.

 

📊 Telling the Story with Data


Data on its own rarely changes minds. But a well told story, grounded in evidence and illustrated with compelling visuals does. A good analyst brings numbers to life. They frame them in a way that connects with people’s goals, hopes, and concerns.

 

🧭 Logical, Thoughtful Thinking


Good analysis is rarely about having the right answer straight away. It’s about having the right approach. Structured, clear, logical thinking turns messy problems into manageable ones. Good analysts bring order to chaos without oversimplifying.

 

🌐 Applying Broad Mental Models


They draw from economics, behavioural science, systems thinking, even history and psychology. Not just to analyse, but to challenge perspective. For example, using the 80/20 principle to prioritise focus, or applying inversion thinking to spot hidden risks. The best analysts don’t just use tools, they use frameworks to see differently.

 

🌀 Being Comfortable With Uncertainty


The path to clarity is rarely clean. Good analysts know that, before things click you must wade through the ambiguity that comes from conflicting data, evolving goals and political tensions. They don’t panic when it’s messy. They trust the process.

 

Every project and every project team needs someone with these skills.


Not just analysts by title - product managers, strategists, consultants, business partners. Anyone responsible for turning complexity into clarity and helping others make better decisions.

 

What do you think?


Have you worked with someone who had these skills?

Which roles do you think benefit most from this kind of mindset?

And what do you think makes a truly great analyst?


👇 Let’s hear your thoughts in the comments.





The answer is - It depends!


While new features drive innovation and revenue, critical bugs can erode trust and operational stability.


Striking the right balance is key and I try to do that by setting clear prioritisation criteria UPFRONT and agreeing it as part of the process going forwards, so decisions are easy, consistent, and only edge cases need escalation.


Our approach:

  1. User & Business Impact First – If a bug affects core functionality, security, or revenue-generating processes, fixing it is non-negotiable. Otherwise, weigh it against new features based on overall impact.  

  2. Strategic Alignment – Does the feature unlock growth, efficiency, or a competitive edge? If so, it may take priority - provided no high-severity issues are in play. Some companies value this more than resource constraints, so weighting must adjust accordingly.

  3. Resource & Timeline Constraints – Sometimes, it's about feasibility. If fixing a critical issue takes two weeks but a feature delivers more value at the same time, I might opt for a phased approach: mitigate the bug immediately while progressing the feature.  

  4. Customer & Team Balance – Listening to both customers and internal teams helps navigate trade-offs. A well-communicated roadmap ensures prioritization decisions make sense to all stakeholders.  

  5. Make it Visual & Actionable – A RAG (Red-Amber-Green) system helps with quick triage, but I adjust weighting based on key factors like external dependencies, compliance risks, or revenue impact.  

  6. Minimize Stakeholder Fatigue – Most stakeholders don’t want to be pulled into every decision. A transparent system keeps things moving while ensuring alignment.  


The main thing to remember - this is not a rigid formula. It’s a framework that evolves with the business. What matters most today may not tomorrow. And no, "because the boss wants it" isn’t a valid weighting factor!


At the end of the day, stability enables innovation, but innovation drives growth - and having the right framework makes the right choice obvious, balancing stability and innovation without it being onerous and contentious!




📌 Today's Quick Lessons Learnt: Time is the one resource we can’t get back. Use it wisely.


Before your next meeting, ask yourself:


  • What’s the clear ask?


  • Does everyone know what’s expected of them?


  • Are we structured enough to achieve our goal in the time we have?


And don’t forget to end the call by checking you’ve actually achieved what you set out to do. Efficiency isn’t just good for business—it indicates you respect the one thing we're all running out of...time.


How do you keep your meetings tight and purposeful? Drop your best tip below 👇


© 2023 by Veraxis Consulting Ltd. Registration no: 15499328. Registered Office: Profile West Suite 2, First Floor, 950 Great West Road, Brentford, TW8 9ES

bottom of page