# Org Topologies in Latvia: Jānis Lāma's Workshops

> Jānis Lāma took Org Topologies to Riga: a workshop at Agile Lounge and a masterclass for 80+ people at the Project Management Conference 2026.

- Author: Jānis Lāma
- Published: 2026-11-22
- Type: case study · industry: Multiple
- Categories: Case Studies
- Canonical: https://www.orgtopologies.com/post/org-topologies-in-latvia-janis-lama-workshops
- Audio: https://www.orgtopologies.com/audio/post/org-topologies-in-latvia-janis-lama-workshops/male.mp3 · https://www.orgtopologies.com/audio/post/org-topologies-in-latvia-janis-lama-workshops/female.mp3

## TL;DR

- This autumn, Jānis Lāma ran two Org Topologies workshops in Riga: one at Agile Lounge (University of Latvia, 30 people) and a masterclass at the Project Management Conference 2026 (80+ people, rated 4.35 out of 5).
- His message: there is no single right org structure. Start with what the strategy asks for, then shape teams, mandates and collaboration to serve it.
- Below: his own view, and what participants took away.

## Scale-Up or Mess-Up?

We have grown in headcount. But have we also grown in our ability to create value for the customer?

Think back to how it all started: the startup. A startup often has a small team with:

- all the skills needed to create value for the customer;
- the full mandate to decide about the product or service;
- direct access to the customer and fast feedback.

But what happens when we start to grow? We split people into functional verticals. Each skill lives in its own box, decision mandates get narrower and narrower, and to create value for the customer, work has to be aligned across countless teams and managers.

And then we ask why everything is so slow, even though we have far more people.

This is exactly where the Org Topologies story begins: how to build an organization whose structure, team [mandates](term:mandate) and way of working together help reach the strategic goals instead of getting in the way.

## Value Flows Across the Boxes

Customer value is not created only inside the vertical boxes of an org chart. It flows horizontally, across functions, departments and teams. Yet many organizations are still built as if value were created in each unit on its own.

Organizations have a clear strategy, ambitious goals and professional people, but they don't get the results they expect. Could one reason be the structure they built themselves?

In a world of growing uncertainty, effective agile teams alone are not enough. To stay ahead, the whole organization needs the ability to adapt, create value and execute its strategy: business agility.

Org Topologies helps here. It is a practical approach to organization design that helps analyze the current structure, find its constraints and deliberately build an organization that supports the business strategy. Its 16 [archetypes](term:archetype) help see different ways an organization can work and how its design affects its ability to create value for the customer.

Instead of rolling out yet another agile framework, it helps answer more important questions:

- Does our structure really support executing our strategy?
- Are teams close enough to the end customer, and do they have the decision mandate they need?
- Do teams have all the skills (business, IT, operations and others) to create value on their own?
- Does our structure foster collaboration and innovation, or does it create needless dependencies and waiting?
- How do we build an organization that adapts faster to the unknown and stays ahead of competitors?

## Agile Lounge at the University of Latvia

On 15 October, we ran an Agile Lounge workshop on organization design with Org Topologies. With 30 participants, we worked through a practical org design case, analyzed its critical elements and explored how different structures affect strategy execution, collaboration and customer value.

I was especially glad to see how actively everyone took part, the positive feedback, and the interest in learning Org Topologies in more depth. Many thanks to the University of Latvia and to Vladimirs Ivanovs, who runs the Agile Lounge events.

![Agile Lounge workshop at the University of Latvia: participants working with Org Topologies maps](https://www.orgtopologies.com/images/posts/org-topologies-in-latvia-janis-lama-workshops/agile-lounge.webp)

Two participants shared their impressions:

> "A practical and engaging format that let us look at how an organization works through real examples: its structure, team composition and skills, dependencies, and their effect on the overall result. Playing out development scenarios made me think about how much the organization's design matters for executing strategy. If you get the chance to take part, I recommend it!"
> — Dita Stirna

> "I had not heard of Org Topologies before, and after this session I really have something to think about in my own work too!"
> — Liene Ieva Kraupsa

## Masterclass at the Project Management Conference 2026

At the Project Management Conference organized by RISEBA University of Applied Sciences, I ran a workshop called "When strategy talks about the future, but the structure is stuck in the past!"

More than 80 people came. The feedback made me happy:

- 4.35 out of 5 on average;
- 82.5% of the ratings were 4 or 5 stars.


There is no single right org structure that fits everyone. It all starts with the strategy: what does it ask of us? Flexibility, innovation and the ability to adapt to the unknown? High predictability and fast delivery? Or cost efficiency and deep expertise in narrow areas?

And then we have to ask: is the structure we built ourselves the biggest obstacle to reaching the strategy? Do teams have the decision mandates and skills they need to create value? Does the way we work together help us reach our goals, or do we create our own obstacles?

Experience shows that this happens far too often. The strategy looks at today and the future, while the structure is still stuck in the past and no longer supports what we want to achieve.

## What Participants Took Away

Diana Rozmane joined the masterclass and summarized eight takeaways:

1. **Most slowness is caused by dependencies, not people.** If work has to pass through three or four teams before it reaches the customer, it will be slow, however well each one works. Ask: how many handoffs are there between an idea and the customer?
2. **Check whether the structure matches what the company says it wants.** If leaders talk about speed and innovation, but everyone sits in narrow specialist groups that aim to be 100% busy, it won't work. A structure always gets what it was built for.
3. **Full utilization and speed are opposite goals.** If predictability and efficiency matter most, specialist groups are a good fit. If fast response to the market matters most, you need teams with all the needed skills in one place. There is no right structure, only one that fits your goal.
4. **Different parts of a company can have different structures.** A stable, mature product and a new experiment don't need the same organization. Forcing one model on everyone is a common mistake.
5. **Doing more doesn't mean achieving more.** More tasks, features or reports done doesn't mean the customer got what they need. Measure results, not busyness.
6. **Start with how work really happens, not how it should.** Before any reorganization, draw the real picture: who does what, who waits for whom, where work stops. Many reorganizations fail because people are moved from one box to another without understanding what is actually broken.
7. **Change is a cycle, not a project with an end date.** Map, assess, try a small change, review. And repeat. The structure is never "finished".
8. **AI changes how much a smaller team can do.** If AI expertise is scattered across departments, with one person here and nobody there, AI product work will stall in waiting. The question is not only "do we have AI?", but "where are the people who know it, and can they work together?"

![Jānis Lāma presenting the Org Topologies map at the masterclass](https://www.orgtopologies.com/images/posts/org-topologies-in-latvia-janis-lama-workshops/masterclass.webp)

Other participants and the organizer wrote:

> "Your sessions are always excellent! This was the fastest-filled workshop. Thank you for creating value!"
> — Inese Sluka, director of the master's programmes in Project Management, Business Management and Health Management at RISEBA University

> "The key idea for me: in large organizations with a historically rigid functional structure, change is objectively too slow. So we need new ways to speed up change and become more adaptable. Cross-functional projects and units are one such way to try."
> — Paulis Dālbergs

> "Thank you for the session! Inspiring and fresh, something to think about!"
> — Diana Andzane

## Continuously Improve Your Organization's Capabilities

One more thing I always try to stress: organization design is not only about reorganizations. It is about continuously improving the organization's capabilities, so that people can breathe more freely, smile more, and together create more value for customers.

Let's 10x our organizations with Org Topologies!

*Jānis Lāma, Outcomly. Based on my LinkedIn posts about [Agile Lounge](https://www.linkedin.com/posts/janislama_orgtopologies-businessagility-organizationaldesign-share-7518313638479466496-zqy2/) and the [Project Management Conference](https://www.linkedin.com/posts/janislama_orgtopologies-organizationaldesign-businessagility-share-7524046180088094721-u69q/), and on [Diana Rozmane's summary](https://www.linkedin.com/posts/diana-rozmane-a1718b97_organizationaldesign-projectmanagement-reorganizaexcija-ugcPost-7522674695574515712-nDvy/).*

## Elevating Katas in this case

- Proposed: [Minimizing Distance to Customers](https://www.orgtopologies.com/elevating-katas#minimizing-distance-to-customers). Participants checked how close their teams are to the end customer and what they may decide.
- Proposed: [Expanding Units Toward End-to-End Outcome Ownership](https://www.orgtopologies.com/elevating-katas#expanding-units-toward-end-to-end-outcome-ownership). Participants checked whether teams hold all the skills to create value on their own.

The full catalog: https://www.orgtopologies.com/elevating-katas.md
