MANAGED CHANGE

Consulting and support

I work with teams and projects in difficult phases: when change becomes heavier, architecture is harder to hold, and there is no internal clarity about what needs attention first.

When I step in

Growth without management redesign

–The company grew faster than its management model.

–Older coordination habits are no longer holding the current load.

The source of the problem is unclear

–Symptoms are visible, but it is still unclear where the problem starts.

–The cause has to be separated from the consequences of accumulated decisions.

Stability depends on specific people

–The system needs constant intervention to keep moving.

–Critical areas depend on specific individuals.

The architecture does not hold together

–Different parts of the system move by their own logic.

–There are solutions, but no coherent architecture.

This work is most useful where the situation needs a deeper look at how the system is actually put together.

Work formats

These two formats cover different depths of work. Situation clarification is for a precise short review. Architectural support is for cases where the system needs steadier work over time.

Situation clarification

A short format for cases where the problem is already visible, but its source is still unclear. The goal is to clarify the situation and define the next step.

1–2 meetings

What people come with

It is not clear where the problem actually starts.

Too many versions, decisions, and interpretations have piled up.

The team needs to see what matters right now.

What happens

We strip away unnecessary interpretation and assemble the factual picture.

We break the situation down into layers: symptoms, causes, and accumulated decisions.

We define a working direction that can actually move.

Result

The situation becomes clearer and overall tension drops.

Focus returns to what actually matters.

The team gets a clear direction for the next step.

Architectural support

A regular collaboration format for cases where one session is not enough and the system needs steady outside support to hold direction over time.

2–4 months of joint work

What people come with

Decisions are made locally and start drifting apart.

Conflicts and extra movement accumulate across teams and roles.

The system needs outside support to move through change without falling apart.

What happens

We align architectural, organizational, and day-to-day logic.

We build stable support around key decisions, roles, and rhythms.

I help the team hold direction as new tensions and changes appear.

Result

The team gets more clarity, coherence, and stability.

Architecture and processes start holding together inside one frame.

The system becomes more resilient to change over time.

These are working formats, not rigid packages. The actual setup depends on the situation and the depth of the request.

Entrypoint

Send a short request in Telegram.

1. What is happening now.

2. Where the most tension is.

3. What result is needed.

4. Why this matters now.

Enough to start. Then I will orient us toward the format that fits.

Write in Telegram