The Lewis Model: Linear-Active, Multi-Active, Reactive Cultures
Turn this article into takeaways for your work.
Each assistant summarizes the article only for you and suggests best practices for your work.
The Lewis Model is a cross-cultural framework by Richard D. Lewis that sorts people by behavior into three types: linear-active (plan and do one thing at a time), multi-active (juggle many things and run on relationships), and reactive (listen first, respond later). Most people are a mix, so you look for the dominant type.
Where Hofstede gives you scores on a scale, Lewis gives you a picture you can recognize in a meeting. Who talks over whom? Who needs the agenda, and who treats it as a suggestion? Who goes quiet because they're listening, not because they have nothing to say?
This guide covers what each type looks like at work, how the model compares with the frameworks you may already use, a step-by-step way to apply it with a real team, a template you can copy, examples by business function, and the places where the model breaks down.
What the Lewis Model Is
Lewis set out the model in his book When Cultures Collide, which Lewis's own consultancy says was published in 1996 and won the US Book of the Month Award in 1997. The same page makes the point that matters most for managers: the model sorts people by behavior rather than by nationality or religion, and it uses three categories, linear-active, multi-active, and reactive.
The book has since gone through several editions. The publisher listing for the third edition describes it as covering more than 60 countries, and says it deals with status, organizational structure, negotiation, sales, and marketing across cultures.
One idea from that source is worth carrying through the rest of this article. Each type contains elements of the other two, and the dominant type is what you plan around. So the model works as a map of tendencies, not a set of boxes.
The Three Types at a Glance
Linear-Active
Lewis describes linear-active people as "task-oriented, highly-organized planners" who work through a chain of actions in a linear agenda. His example regions include the English-speaking world (North America, Britain, Australia, New Zealand) and Northern Europe, including Scandinavia and the Germanic countries.
At work, that tends to look like punctual starts, written agendas, one topic at a time, and a belief that a deadline is a commitment. A linear-active manager often reads a long interruption as disrespect for the plan.
Multi-Active
The same source describes multi-active people as "emotional, loquacious and impulsive," valuing family, feelings, and relationships, multitasking, and being "poor followers of agendas." Example regions listed include Southern Europe, the Mediterranean, South America, sub-Saharan Africa, the Arab and wider Middle East, India and Pakistan, and most Slavic cultures.
At work, that can mean several conversations running in parallel, a meeting that wanders into relationships before it gets to business, and plans that bend when something more important to a person turns up. To a multi-active manager, a rigid agenda can feel like a refusal to deal with what's actually going on.
Reactive
Lewis calls reactive people "good listeners, who rarely initiate action or discussion." They first establish the other person's position, then react and form their own view. The page places major Asian countries here, and treats the Indian sub-continent as a hybrid.
At work, that tends to look like long listening, careful courtesy, few interruptions, and opinions that surface after the meeting rather than in it. A reactive colleague who stays quiet is often gathering information, not withholding it.
Quick Comparison of the Three Types
| Trait | Linear-active | Multi-active | Reactive |
|---|---|---|---|
| Core stance | Plan, then act | Engage with everything at once | Listen, then respond |
| Time | A resource to schedule | Flexible, set by people and priorities | Cyclical and patient (a tendency, not a rule) |
| Agenda | Followed | A starting point at best | Respected, but rarely challenged aloud |
| Talking | Takes turns | Overlaps, interrupts | Waits, rarely interrupts |
| Information | Documents and facts | Conversations and relationships | Listening and indirect signals |
| Trust built by | Reliability and meeting commitments | Personal rapport | Consistency and courtesy over time |
| A late start means | Disrespect | Something more important came up | Politeness to whoever is still talking |
The "Time" and "Late start" rows for the reactive column are interpretive summaries, not Lewis quotes. Treat every cell as a hypothesis to test.
Lewis vs Hofstede vs Trompenaars vs Meyer vs Hall
Lewis is one of several frameworks that try to make cultural difference usable. They answer different questions, which is why using two together often beats picking one.
| Framework | Unit it describes | What it gives you | Best used for |
|---|---|---|---|
| Lewis Model | Behavior types (three) | A recognizable picture of how people plan, talk, and listen | Preparing for meetings, negotiations, and team norms |
| Hofstede | Countries, scored on six dimensions | Numbers you can compare and cite | Market entry, org design, quick country comparisons |
| Trompenaars | Cultural dilemmas (universalism vs particularism and others) | Questions that surface value conflicts | Resolving why two sides keep misreading each other |
| Erin Meyer's Culture Map | Scales on which any two cultures can be placed | A way to place two specific cultures side by side | Day-to-day team management: feedback, disagreement, scheduling |
| Hall's high and low context | Communication style | How much meaning sits in words vs in the situation | Written and spoken communication choices |
A short way to choose: reach for Hofstede when you need numbers, Meyer when you need to compare two specific cultures, Hall when the problem is how messages get understood, and Lewis when you need a quick, memorable read on how a meeting or project will feel. Lewis also lines up neatly with Hall's high-context idea on the reactive and multi-active side, and with low-context on the linear-active side, though the two models were built differently and don't map one to one.
How to Use the Lewis Model With a Team: Step by Step
The model earns its keep when you use it to adjust your own behavior, not to label other people.
- Start with yourself. Write down how you actually run a day: do you work from a list, jump between conversations, or hold back until you've heard everyone? Your honest answer shows which type you default to and where you'll cause friction.
- Describe behaviors, not nationalities. Ask each team member how they prefer to handle agendas, interruptions, deadlines, and silence. Behavior sits at the center of the model, so start there.
- Plot the team. Mark each person as leaning linear-active, multi-active, or reactive, with a note on their second tendency. Use the template below and keep it private to the team lead until people have checked their own entries.
- Find the friction points. Look for pairs that will clash. A linear-active project manager paired with a multi-active supplier is a classic one, as is a multi-active sales lead paired with a reactive buyer.
- Agree three team norms. Pick explicit rules on the things that cause most trouble: how agendas are used, whether interruptions are welcome, and how people signal disagreement.
- Build in a bridge for each type. Give linear-active people the agenda and written follow-up they need, multi-active people room for relationship time, and reactive people a way to contribute after the meeting.
- Review after four to six weeks. Check which norms held, which didn't, and update the template. Treat the first version as a hypothesis, not a diagnosis.
Template: Team Culture Profile (Copy and Use)
Copy this table into your team doc and fill in one row per person. Add a second tendency, since the model expects blends.
| Name | Role | Dominant type (L / M / R) | Second tendency | Preferred way to run meetings | Preferred way to give input | Friction risk with | Bridge action |
|---|---|---|---|---|---|---|---|
A second table, for agreeing norms once you've seen the pattern:
| Norm | Our rule | Who it protects | Review date |
|---|---|---|---|
| Agenda use | e.g., sent 24 hours ahead, treated as a guide | ||
| Interruptions | e.g., allowed for clarifying questions only | ||
| Silence in meetings | e.g., written input accepted for 24 hours afterward | ||
| Deadlines | e.g., one named owner, flags raised early | ||
| Disagreement | e.g., raised in the meeting or in a private message |
Examples by Business Function
The scenarios below are illustrations of how the types can play out. They're hypothetical, not case studies, and any individual may behave differently.
Sales
A linear-active seller may open with a clear agenda and move to a proposal in the first meeting. With a multi-active buyer, that pace can feel like being pushed past the relationship. Spending the first meeting on the buyer's context and priorities usually costs less than a stalled deal. With a reactive buyer, silence after a pitch rarely means no. A follow-up that restates the proposal in writing, without pressure, tends to land better than a chase call.
Negotiation
Linear-active negotiators tend to want a sequence: positions, concessions, close. Multi-active counterparts may reopen settled points as relationships and circumstances shift. Reactive counterparts may listen to your whole case before showing any position. Plan for different pacing: build a written record of agreed points for the first, expect revisits with the second, and give the third space to reply. If you're working across the three, our guide to relationship-first vs task-first cultures goes deeper on sequencing trust and business.
Meetings
A linear-active chair will run to the agenda and the clock. A multi-active attendee may answer a text, take a call, and still follow the discussion. A reactive attendee may wait until the end to speak. A workable compromise is a short agenda with timed items, an explicit "parking lot" for tangents, and a written channel for follow-up comments.
Project Management
Linear-active teams plan in phases and treat milestones as commitments. Multi-active teams may re-sequence work when a more urgent relationship need appears. Reactive teams may avoid saying a deadline is at risk until they're sure. For mixed teams, schedule short check-ins, ask "what could slip?" as a standing question, and make it safe to answer honestly.
Customer Support
A linear-active support agent follows the ticket process step by step. A multi-active customer may phone, email, and chat all at once about the same issue. A reactive customer may not complain at all, and just go quiet. Give agents room to acknowledge the whole situation first, and use proactive check-ins rather than waiting for the customer to escalate.
Leadership Feedback
Linear-active leaders tend to give feedback plainly and expect it to be taken as information. Multi-active leaders may wrap it in conversation and relationship. Reactive leaders may imply rather than state. If your feedback is direct and your team's isn't, read our guide on direct vs indirect feedback across cultures before the next review cycle.
Do's and Don'ts
| Do | Don't |
|---|---|
| Treat the types as tendencies and hold them loosely | Assume a person behaves like their country's average |
| Ask people how they prefer to work | Guess from their passport or accent |
| Agree team norms out loud | Rely on everyone adapting silently |
| Give each type something they need: a written agenda, relationship time, or space to reply | Push everyone into your own style |
| Revisit your read after you've worked together | Lock in a label after one meeting |
| Pair the model with a second framework such as Hofstede | Use one model as the whole answer |
| Read silence and interruptions as possible styles | Read them automatically as disengagement or rudeness |
Limitations of the Lewis Model
Every cultural model simplifies, and this one deserves a clear-eyed look.
It's a typology, not a measurement. Hofstede gives you a score for each country. Lewis gives you three types and example regions. That makes the model easy to remember and quick to use, but it can't tell you how far a particular person or country sits from the center of a type. Lewis's own site is explicit that each type contains elements of the other two, so any one-word label is a simplification by design.
The source material is mostly Lewis's own. The model's evidence base, as Lewis's consultancy describes it, is questionnaire data from executives and online respondents across 68 nationalities. That's a large pool, but it's an employed, business-facing one, and it's presented by the model's author rather than by independent replication. Treat the model as a useful practitioner's tool and a good source of hypotheses, not as settled social science.
Regional groupings blur real variation. Grouping "most Slavic cultures" or "major Asian countries" under a single type hides large differences between countries, industries, generations, and individuals. A software engineer in Seoul and a family-business owner in Jakarta may share a region and almost nothing else about how they work.
Behavior shifts with context. The same person can be linear-active in a regulated finance process and multi-active in a founder-led sales team. Company culture, role, and seniority all pull against national tendency.
It can slide into stereotyping. The fastest way to misuse the model is to treat it as a prediction. Use it to prepare a question, not to deliver a verdict.
Putting It Together
If you only remember three things, make them these. First, the model is about behavior, and behavior can be observed and asked about. Second, the dominant type is a starting hypothesis, and you update it as you learn the people. Third, the goal is smoother work, so agree norms the whole team can live with and use a second framework when stakes are high.
For the wider picture of how culture differs between teams and countries, start with managing a multicultural team, then look at communication styles across cultures for the day-to-day mechanics.
Key Facts
- Richard D. Lewis set out the three-type model in When Cultures Collide, published in 1996 and the winner of the US Book of the Month Award in 1997. Source: crossculture.com
- The model sorts people by behavior rather than nationality or religion, using three categories: linear-active, multi-active, and reactive. Source: crossculture.com
- Lewis's consultancy says the model draws on data from 50,000 executives on residential courses and more than 150,000 online questionnaires covering 68 nationalities. Source: crossculture.com
- The third edition of When Cultures Collide, published by Nicholas Brealey, covers more than 60 countries. Source: crossculture.com
- Each cultural type contains elements of the other two, so the dominant type is what matters in practice. Source: crossculture.com

Co-Founder, Rework.com
On this page
- What the Lewis Model Is
- The Three Types at a Glance
- Linear-Active
- Multi-Active
- Reactive
- Quick Comparison of the Three Types
- Lewis vs Hofstede vs Trompenaars vs Meyer vs Hall
- How to Use the Lewis Model With a Team: Step by Step
- Template: Team Culture Profile (Copy and Use)
- Examples by Business Function
- Sales
- Negotiation
- Meetings
- Project Management
- Customer Support
- Leadership Feedback
- Do's and Don'ts
- Limitations of the Lewis Model
- Putting It Together