A project is behind and the team is arguing about why. In the first ten minutes of that meeting, what do you actually do?

Cut the debate off and assign who owns what before anyone leaves.

Get people talking so the tension drops before we try to fix anything.

Ask quietly what each person needs, and protect whoever is getting steamrolled.

Pull up the plan and show exactly where the slip started.

You disagree with your manager's decision, in a room of eight people.

Say nothing there, and raise it one-on-one afterwards.

Say so, in the room, right then.

Ask for the reasoning and the numbers before taking a position.

Make the counter-case with a joke first, so it lands lighter.

A new process rolls out on Monday. What is your first question?

Where's the doc? I want the edge cases before Monday.

What happens to the people who liked the old way?

What's the deadline, and who's accountable?

Who's already on board, and how do we get the rest excited?

What does your calendar actually look like?

Overbooked with people — I say yes to almost every conversation.

Blocked precisely, with prep time before anything that matters.

Deliberately loose, so I can jump at whatever matters most today.

Steady and repeatable — the same rhythms week to week.

A teammate hands you work that is 80% right.

Quietly fix the small things rather than make it a thing.

Send line-level comments with the standard attached.

Lead with what worked, then coach the rest in conversation.

Tell them the missing 20% straight, then move on.

Something you owned publicly failed. It's the week after.

Write the post-mortem: root cause, timeline, prevention.

Talk to everyone affected and keep the relationships intact.

Decide the fix and ship it fast.

Absorb it, keep the team steady, carry the blame myself.

A bet with a 50% chance of a big win.

Take it — standing still costs more.

Not until I've modeled what happens when it fails.

Take it if I can get people fired up about it.

Only after I've protected the team from the downside.

In a meeting where nobody is talking, what do you notice first?

The flat energy — I'll get someone laughing.

Who looks uncomfortable — I'll draw them in.

That the question was vague — I'll restate it.

That we're wasting time — I'll force a decision.

How do you want feedback about yourself?

Written, specific, with examples I can check.

Blunt, one sentence, no cushion.

Private, gentle, with time to think it over.

In conversation, warm, with room to react.

Two peers are in a real conflict and both come to you.

Listen to each separately and find the compromise nobody loses.

Reframe it as a misunderstanding and rebuild the goodwill.

Get them in one room and make the call.

Separate fact from interpretation, then set a rule so it can't recur.

Under real pressure, what do colleagues notice first about you?

I withdraw into the detail and re-check everything.

A year from now, you'd be proud if:

People say working here changed something for them.

What we built still runs with no surprises.

The team is still together and nobody burned out.

We hit a number nobody thought we'd hit.

Which of these is closest to your role?

I'm an external coach or consultant assessing a client

DISC Personality Test: What's Your Behavioral Style at Work?

Twelve questions, about three minutes. Not "how would you describe yourself" but "what did you actually do last time" — your answers score four dimensions and return a radar of how you work.

D · Drive — decides fast, says the uncomfortable thing first
I · Influence — moves people, builds momentum in a room
S · Steadiness — keeps the team upright, absorbs the shocks
C · Conscientiousness — raises the standard, catches what others miss

You'll get your strongest and weakest dimension, the blind spot that comes with your style, one thing to try this week, and how to work with the other three. It works best across a whole team: everyone answers separately, then you compare.

DISC describes behavior, not ability. It is not a hiring, clinical or diagnostic instrument.