I Thought I Had Finished the Task. My Boss Thought Otherwise (Abstract Vs. Concrete on Teamscape)

I spent three days creating a framework for client onboarding. 

The result was a conceptual model showing how different client types flow through our system. 

Clear. 

Strategic. 

Complete. 

My boss looked at it and said: "Where are the actual steps?"

I thought I'd finished. She thought I'd barely started.

This happens constantly in teams. Leaders get frustrated thinking people didn't complete work. Team members get frustrated thinking they delivered exactly what was asked for.

Look at this team's Dimension 4 (Sense Making) map:

Everyone clusters in the abstract zone (top). They think in concepts, frameworks, big picture. They need to understand the "why" before moving.

No one sits in the systematic zone (bottom right). No one naturally builds step-by-step processes.

The Tension

You ask Person 3 to "create an onboarding process." They give you a conceptual framework. You wanted a checklist. 

Both of you are right. And frustrated.

You tell Person 8 to "just get this done." They spend two days understanding the context. You wanted immediate action.

What Teamscape Makes Concrete

When a leader looks at the Teamscape maps, it's easier to stop assigning systematic work to people who think abstractly. Now, you know the difference and you know what kind of work is best suited for the team you currently have.

A practical next step could be to either hire for the gap in the team or redesign work to match how your team actually operates.

It's easy to blame the frustration on laziness or incompetence. 

In reality, it's mismatched expectations you couldn't see until now.

Context: Teams complete a 10-minute Teamscape® assessment that maps how they naturally work together across four key dimensions.