Builder Orientation Profile

When my team has more commitments than capacity for them, I push to take something off the list.

My first response to a new request is to weigh it against what we have already committed to.

When a goal or meeting feels low-value, I say so and push to cut it.

I am usually the person asking what we are not going to do.

When I am pulled in too many directions, I draw a hard limit on one or two priorities and let the rest wait.

When I sense two colleagues are working from different assumptions, I name it before it escalates.

When I communicate a decision, I think about how the people who were not in the room will hear it.

I can usually tell when someone says they agree but does not actually agree, and I address it.

When goals change, my instinct is to rebuild a shared picture with the team rather than just send an update.

I tend to bridge people who are technically talking about the same thing but not actually understanding each other.

When it is unclear who should make a decision, I am typically the one to name who should own it.

I notice when people are doing work they were not authorized to do, or avoiding work they were.

When a decision stalls, I diagnose whether the problem is missing information or unclear ownership.

I push for decisions to be made at the level closest to the work, even when that means giving up control.

My first question when work is stuck is who owns this, not what should we do.

After something goes wrong, my instinct is to understand why the system produced it, not who made the mistake.

When people resist a change, I treat their resistance as data worth understanding.

I notice when my team is solving the same problem repeatedly in slightly different forms.

I invest real effort in developing the people around me and passing on what I know.

When a plan is not working, I push for a different approach rather than trying harder with the same one.