Analyst

You work carefully and deeply. Give you a problem and you want to understand it properly first: what the data says, what has been tried, where the risks are. You prefer to go deep on one thing rather than skim many, and you would rather write a solid plan than improvise.

You double-check your work before sharing it. You notice the inconsistency in the figures, the clause that does not quite fit, the step that will break under pressure. That is why people trust what you deliver, and why your name on a document carries weight.

You like clear processes. Not for their own sake, but because they make good work repeatable. When a system works well, you feel a quiet, real satisfaction. You would rather solve a problem once, properly, than patch it every week, and over time your teams spend far less energy firefighting.

Your ideal week has long stretches of focus. Monday starts with clear priorities and time to plan. Tuesday and Wednesday are mostly uninterrupted: deep work on a complex problem, with notifications off and a closed door or headphones on.

There are a few meetings, but they have agendas and clear purposes, and you have had the materials beforehand. You can come prepared, and the decisions made are ones you have had time to think about.

On Thursday you review, test and refine. On Friday you share something finished and solid, and you get thoughtful questions about it rather than rushed reactions.

What you do not want is a week of constant interruptions, last-minute changes and pressure to decide something important with half the information. That kind of week leaves you drained and uneasy, even if you got through it.

In meetings you are the careful voice. You ask the questions others did not think of: "What does the data say?" "What happens if this fails?" You often stay quiet while ideas fly, then raise the point that changes the decision. People have learned that when you speak, it is worth listening.

You prefer meetings with an agenda and pre-reading. You do your best thinking before and after, not in the moment, and you may leave a meeting with your best idea arriving on the walk back to your desk.

The risk is that your best point arrives too late, or sounds like a block rather than a help. Try two habits. Send your thoughts in writing beforehand, so they are on the table early. And frame concerns as improvements: "This could work even better if we checked X first." It keeps your rigour welcome rather than dreaded.

As a leader you are thoughtful, fair and rigorous. Your team knows that decisions are based on evidence, not mood. You set clear standards and processes, and work under you tends to be high quality and low drama.

People trust you because you do your homework. You rarely make a rash call, and you protect your team from avoidable mistakes. You are also fair: people know that good work will be noticed, because you look closely.

The growth edge is speed and visibility. Teams sometimes need a quick decision and a bit of inspiration. Practise deciding with good-enough information and a plan to adjust. And share your thinking out loud more often, so your team can see your reasoning and feel part of it. A short weekly note explaining what you decided and why will do more for morale than you might expect.

As a teammate you are the safety net. You check the details, catch the errors and make sure the work holds up. Colleagues often ask you to review things because they trust your eye, and many disasters have been quietly prevented by your second look.

You are reliable and thorough. When you say something is done, it is done properly. You also tend to be the person who knows where things are and how they work.

The thing to watch is holding work too long. Your standards are high, and you might keep polishing when the team needs something now. Try sharing earlier versions with a note: "This is an early version. Any big gaps?" It invites help and keeps things moving without lowering your standards. You may also find colleagues spot things you had not, which saves you time.

With a Driver, you share a focus on the task, but you differ on speed. They want to decide now. You want to check first. Agree a deadline for your analysis, and give them your recommendation clearly, headline first. Your rigour plus their pace makes a strong team.

With an Explorer, you sit at opposite corners. They bring lots of fast ideas. You bring depth and caution. That can feel chaotic, but it is valuable. Let them generate options, then help them choose the best one and test it properly. Try not to critique every idea in the first ten minutes. Let the brainstorm breathe before you start testing.

With a Connector, you share a deliberate pace. They focus on people, while you focus on the work. Ask them how a plan will land with the team. They will help your solid plans get real buy-in, and you will help their people plans hold up.

You are stressed by chaos, rushed decisions and sloppy work. Changing priorities, missing information, constant interruptions and being asked to sign off on something you have not checked all drain you heavily. Being blamed for a mistake you warned about is particularly hard.

Under stress you may withdraw and dig deeper into detail. You might over-check, become critical of others' work or freeze when a decision has to be made quickly. You can also become quietly frustrated without saying why, which leaves colleagues guessing.

The best reset is to restore some order. Write down what you know, what you do not know and what you need. Then ask for the time or information you need, plainly and early. Most people will give it once they understand. Protecting one block of uninterrupted time, even an hour, can also bring your thinking back into focus.

Share this with your team, or use it to explain yourself. It helps people get your best thinking rather than your rushed thinking.

• Send it in advance. I do my best thinking with the materials before the meeting.
• Give me time to check. A short deadline is fine. No deadline at all is not.
• Bring the data. I am persuaded by evidence more than enthusiasm.
• Let me focus. Batch your questions where you can. Interruptions cost me more than you think.
• Ask for my view directly. I may not interrupt to give it, but I will have one.
• Tell me what good enough looks like. It helps me know when to stop polishing.
• Don't take my questions personally. I am testing the idea, not you.
• Warn me about changes. A heads-up the day before beats a surprise in the meeting.