When to Hire a Narrative Consultant

When the problem is no longer a lack of ideas, but understanding the situation well enough to know what is missing

A wall is covered in answers.

Research notes. Character maps. Audience profiles. historical material. Brand language. Plot lines. Workshop results. Product ideas. A timeline. Three different visions of what the project is supposed to become.

Everyone in the room has contributed something valuable.

And yet somebody eventually asks the uncomfortable question:

> “What are we actually trying to solve?”

That is often the moment when consulting becomes useful.

Not because a project has run out of ideas.

Often it has too many.

Not because the people involved are incapable.

Often they are specialists who understand their own parts extremely well.

The problem appears when history, worldbuilding, storytelling, behaviour, systems, audience, identity and intended experience no longer fit together clearly enough for anyone inside the project to see where the real friction lies.

That is not necessarily a writing problem.

It may not even be a narrative problem.

It is a situation that needs to be understood.

And good consulting starts there.

> Do not begin with the solution. Begin with the situation.

First ask where you are coming from

Every project already has a history before a consultant arrives.

A company may have existed for forty years.

An intellectual property may have crossed several editions, authors and media.

A museum may inherit decades of scholarship and curatorial decisions.

A game may have accumulated years of canon, mechanics and community expectations.

A historical site may carry several centuries of documented events, folklore and later reinterpretation.

A creative team may simply have spent eighteen months building something together.

None of that disappears because somebody decides that the project needs to change.

So the first question is not:

> “What should we create?”

It is:

> Where are we coming from?

What already works?

What does the project believe about itself?

What do the people around it believe?

Which decisions created the present situation?

Which values are genuinely structural and which are merely habitual?

Which parts of the past still exert pressure on the present?

Which things are remembered differently by different people?

What must be protected because losing it would destroy the identity of the project?

History is not background decoration.

The present is carrying it whether anyone acknowledges that or not.

Then ask what you actually want

This is often harder than it sounds.

Clients frequently arrive with solutions disguised as problems.

> “We need more storytelling.”

Perhaps.

> “We need a new website.”

Maybe.

> “We need to rebuild the world.”

Possibly.

> “We need a rebrand.”

Why?

The requested intervention is not necessarily the actual need.

A company asking for better storytelling may really be struggling because its public identity and internal behaviour contradict one another.

A publisher asking for more lore may actually have an accessibility problem.

A museum asking for more historical material may already possess too much information and too little interpretive structure.

A game studio asking for stronger factions may have excellent factions whose actions are simply invisible to players.

A creative team asking for more ideas may really need to decide which ideas still belong to the project.

> Do not solve the requested solution before you understand the actual need.

So consulting asks a more difficult question:

> What are you actually trying to achieve?

More information?

More understanding?

A stronger sense of identity?

Different behaviour?

Greater participation?

Better continuity?

A more coherent world?

A new audience?

A transition into another medium?

A project that can grow without losing what made it valuable?

Until that becomes clear, almost any intervention risks being activity without direction.

Where do you want to go?

A destination should not only be described as a deliverable.

“New website.”

“New campaign.”

“New exhibition.”

“New edition.”

“New brand strategy.”

Those are outputs.

The more useful question is:

> What should be different when this succeeds?

What should people understand that they do not understand now?

What should they notice?

What should become easier to do?

What should they care about?

What should they remember?

What kind of behaviour should the surrounding system make possible?

What should people tell someone else after experiencing the result?

That last question is often particularly revealing.

An organisation can describe itself perfectly in a strategy document and still produce a completely different story through lived experience.

A museum can intend to show the complexity of ordinary medieval life while visitors leave remembering only swords and kings.

A game can advertise that choices matter while the world looks exactly the same after every major decision.

A company can promise autonomy while requiring seven approvals for a minor action.

The intended message may be clear.

The lived situation tells another story.

Analyse the situation, not just the story

This is where narrative consulting becomes larger than writing.

A useful way to look at a situation is to follow what happens between reality and consequence:

> Situation → Perception → Understanding → Interpretation → Action → Response → New Situation

Something exists.

People encounter part of it.

They understand something from what they encounter.

They interpret that understanding through their own experience, expectations, culture, interests and history.

They act upon that interpretation.

The surrounding world, organisation, system or community responds.

That response creates the next situation.

Then the cycle begins again.

The important question is:

> Where is the friction?

Sometimes the initial situation itself cannot support the desired result.

Sometimes the right information exists but people never notice it.

Sometimes they notice it but lack the context to understand it.

Sometimes they understand it but interpret it differently from what was expected.

Sometimes they understand exactly what is intended but have no meaningful way to act upon it.

Sometimes they act and receive no response.

Sometimes a response happens but remains invisible.

All of those problems can look from a distance like:

> “Our storytelling is not working.”

They are not the same problem.

And they should not receive the same solution.

A museum may not need more information

Imagine an exhibition about a medieval city.

The scholarship is excellent.

The artefacts are authentic.

The dates are correct.

The curators want visitors to understand that the city was a network of merchants, labourers, religious communities, migrants, families, guilds and political interests.

Visitors leave remembering three weapons and one king.

That is useful evidence.

The immediate reaction might be:

> “We need to explain more.”

But perhaps more explanation would make the problem worse.

The consultant asks:

What receives the most visual attention?

Which objects occupy the centre of the room?

Whose lives are personified?

What connections can visitors actually perceive?

What does the spatial design implicitly tell them is important?

What do visitors repeat afterwards?

Perhaps the historical research is not failing at all.

The experience is organising that research into a different hierarchy of meaning.

The solution may therefore involve interpretation, space, perspective or visitor interaction rather than adding another panel of text.

> More content does not repair a problem caused by the way existing content is experienced.

A company may not need a better story

Imagine a company that wants a culture of initiative.

Leadership communicates the idea clearly.

Employees understand it.

Many even agree with it.

But meaningful decisions still require several layers of approval.

The resulting cycle is predictable.

Employees perceive the approval structure.

They interpret caution as safer than initiative.

They behave cautiously.

Leadership observes little initiative and concludes:

> “Our people need to become more entrepreneurial.”

Now somebody proposes a new internal storytelling campaign about empowerment.

But the story was not the primary problem.

The structure contradicted it.

> If the problem is structural, do not sell storytelling as the cure.

Sometimes the most useful conclusion a consultant can reach is:

> “This is not my problem to solve.”

Good consulting includes recognising when the required intervention belongs to another discipline.

Worldbuilding is not limited to fictional worlds

Worldbuilding also becomes much larger once we stop treating it as a fantasy-writing term.

Every complex environment has conditions within which people interpret and act.

A fictional city has institutions, geography, social rules and history.

So does an organisation.

A museum.

A historical site.

A community.

A festival.

A large live event.

A brand ecosystem.

A transmedia project.

The question is not whether these things are fictional worlds.

The question is whether people must navigate a meaningful environment containing rules, relationships, identities, expectations and consequences.

Worldbuilding becomes useful whenever we need to understand:

> What world are people actually entering?

What assumptions does it teach?

What behaviour does it reward?

What relationships does it make possible?

What history does it carry?

Where does formal authority differ from real Influence?

What can change?

What cannot?

And what does the environment communicate before anybody explicitly explains it?

Different people inhabit different versions of the same situation

A further difficulty appears because there is rarely only one interpretation.

Consider a company after a merger.

Senior management may describe the event as transformation.

One group of employees experiences it as expansion.

Another experiences it as loss.

Customers may see improved services.

Long-term clients may believe the organisation has abandoned what once made it distinct.

None of these perspectives can be understood purely by rewriting the corporate history.

People interpret a situation through where they stand inside it.

Their role matters.

Their history matters.

Their interests matter.

Their previous experiences matter.

Their losses matter.

Their expectations matter.

The same is true in a creative project, a community, an exhibition or an intellectual property.

> Understanding the situation requires understanding who is experiencing which part of it, from where, and with what history.

That does not mean every interpretation is equally accurate.

It means interpretation itself is part of the situation.

Sometimes every component is good and the whole still fails

This is one of the strongest reasons to bring in an outside perspective.

A game can have excellent mechanics.

Excellent writers.

Excellent lore.

Excellent art direction.

Excellent characters.

And still produce an experience that feels strangely disconnected.

A company can have capable departments and still create a confusing customer journey.

An exhibition can contain brilliant research and exceptional objects but never form a coherent experience.

A transmedia property can produce several strong products that somehow stop feeling like the same world.

> Sometimes every part works and the whole still does not.

The problem lives between disciplines.

Mechanics may not reinforce fiction.

Research may not survive translation into experience.

A brand promise may not survive operational behaviour.

A historical interpretation may not fit the physical experience of a site.

A story may work beautifully in prose and collapse when moved into an interactive medium.

Those are exactly the situations where adding another specialist inside the existing silo may not be enough.

Someone has to look at the relationships between the parts.

The right intervention may come from somewhere else

This is also why consulting should never begin with a fixed toolbox.

The problem may need:

historical research.

anthropology.

game design.

UX.

facilitation.

information architecture.

organisational change.

continuity work.

worldbuilding.

storytelling.

audience research.

education design.

technical expertise.

or something else entirely.

The consultant does not need to pretend to be the best specialist in every field.

The more valuable skill is recognising what kind of question has appeared.

> Find the weakness. Find the specialist. Borrow the tool. Keep the soul.

Sometimes that means bringing in another expert.

Sometimes it means using a method from another discipline.

Sometimes it means telling the client that the solution is already inside the organisation and merely needs to be recognised.

The goal is not to force every problem through the consultant’s favourite framework.

The goal is to solve the actual problem.

Facilitation, consulting and design are not the same thing

These roles can overlap, but it helps to distinguish them.

Facilitation helps people work through a process together.

It can make competing perspectives visible, improve discussion, help a group make decisions and prevent the loudest voice from automatically becoming the only voice.

Consulting helps diagnose the situation.

What is happening?

Why?

What are we trying to change?

Where is the friction?

What kind of intervention is appropriate?

Design builds or changes the structures through which the desired experience can emerge.

One person may sometimes perform all three roles.

But recognising the difference prevents a workshop from being sold as diagnosis, or a design solution from being imposed before anyone understands the problem.

Consulting is useful before things break

Another misconception is that consultants are only brought in when something is failing.

Growth creates complexity too.

A small project becomes an organisation.

A single game becomes a product line.

One successful event becomes several.

A local community becomes international.

A fictional setting moves into another medium.

A founder-led creative process becomes a team process.

Suddenly assumptions that were manageable when five people understood everything informally no longer scale.

> Success creates complexity too.

Consulting can therefore be preventive.

What made the project work?

Which parts are essential?

Which processes existed only because specific people happened to know one another?

What must become explicit before growth destroys something that originally emerged naturally?

Sometimes the best time to ask for another perspective is precisely when everything appears to be going well.

The consultant should not become permanent machinery

There is one more distinction that matters.

A consultant can identify a problem.

A consultant can help build a solution.

A consultant can work closely alongside a project while that solution is tested.

But if every future problem of the same type still requires the consultant to explain what is happening, something important has been missed.

Good consulting should increase the client’s ability to see.

At the beginning, the work may be close and hands-on.

Questions are explored together.

Patterns are made visible.

Tools are explained.

Interventions are tested.

The consultant remains available when the situation changes or when a harder problem appears.

But over time, the relationship should mature.

The client begins noticing patterns earlier.

They learn which questions to ask.

They recognise when a problem can be handled internally.

They recognise when they lack information.

They recognise when another discipline is required.

And they recognise when bringing the consultant back in is genuinely useful.

> Do not just solve the current situation. Help people develop the judgement to recognise what the next situation requires.

This does not mean teaching everyone to become a consultant.

It means building enough understanding that people are no longer dependent on someone else to tell them that something is missing.

The goal is maturity

Maturity does not mean doing everything alone.

It means being able to make a better judgement about what the situation requires.

> The goal is maturity: knowing what you can recognise, what you can solve, what is still missing, and when another perspective will genuinely help.

A mature team can say:

> “We can handle this internally.”

Or:

> “We understand the problem but need specialist research.”

Or:

> “This is not a storytelling problem at all.”

Or:

> “We have reached the limit of our current tools. We need another perspective.”

That is not a failure of consulting.

It is one of its best outcomes.

Good consulting should leave a client better prepared for the next situation than they were for the first.

So when should you hire a narrative consultant?

Not simply when a story is bad.

Not when you run out of ideas.

Not because another layer of professionalism automatically improves everything.

Consider outside help when the relationships between history, identity, world, people, systems, behaviour and intended experience have become difficult to read from inside the project.

When you know something is wrong but cannot locate the mechanism producing it.

When several excellent components no longer form a coherent whole.

When growth is beginning to strain the structures that once worked.

When a project is moving into a new medium, audience or cultural context.

When different groups are living inside sharply different interpretations of the same situation.

When the solution being requested may not be the solution actually required.

Or when a project matters enough that understanding the problem properly is cheaper than repeatedly treating its symptoms.

The work begins with simple questions:

> Where do you come from?

> What do you actually want?

> Where do you want to go?

Then comes the harder work:

What is happening now?

How is it being perceived?

How is it understood?

How is it interpreted?

What action follows?

How does the surrounding world respond?

What situation does that response create next?

Somewhere in that cycle, the real problem often becomes visible.

Then we can decide what belongs there.

A story.

A system.

Research.

Worldbuilding.

A workshop.

A structural change.

Another specialist.

Or perhaps nothing more than a clearer understanding of what was already working.

A consultant should not arrive merely with a better story.

They should help you see the situation well enough to understand what it needs now — and gradually become better at recognising what it will need next.

Stories that remember. Worlds that change.

Read: https://mythveilchronicles.com/ Play: https://startplaying.games/gm/dunchan Watch: https://www.youtube.com/@MythveilChronicles Support: https://www.patreon.com/MythveilChronicles Collaborate: https://www.linkedin.com/in/francisco-jos%C3%A9-z-b05aab371/