Internal alignment

Who Needs to Say Yes? A Stakeholder Map for Your Japan Pilot

 By the GLOBAL MUSIC PARTNERSHIP editorial team / Supervised by Naoto Tanaka (Tarnar sensei)

Many cross-border projects slow down not because of the partner but because of an unnoticed approval at home. A one-page stakeholder map shows who needs to say yes, and when, before you commit.

Before you contact a partner in Japan, draw a one-page map of the people on your own side: who can say yes, who must be consulted, who simply needs to know, and at which step of the process each of them is involved. The partnership process has five steps, from first contact to a signed agreement, and a map like this makes sure that nobody is surprised at step five by a question that could have been answered at step one.

Why the map matters more in cross-border work

When both sides are in the same city, a missing approval is fixed with a corridor conversation. Across time zones and languages, the same gap can cost a week. A question lands in the inbox at the end of the partner's day, reaches the right person on your side the next morning, waits for an answer, and returns another day later.

The partnership desk helps by keeping early steps light. The first online meeting, the rights and goals conversation and a small pilot all come before any larger commitment, and the written proposal with the cost and the payment schedule arrives after the first online meeting. That order gives you time to bring colleagues along. A stakeholder map is how you use that time well.

The four kinds of people on the map

Start by sorting people into four kinds. The sorting is quick, and it changes the way you talk to each person, because a decider needs a clear choice, a contributor needs a clear task, an adviser needs a clear question and an observer needs a clear update.

KindMeaningTypical people
DeciderCan say yes or no to the pilot, the budget or the agreementOwner, director, head of school, festival producer
ContributorDoes part of the work or controls part of the materialArtists, teachers, engineers, programmers
AdviserGives an opinion that must be heard before a decisionLegal adviser, finance lead, rights manager
ObserverNeeds updates but no approvalColleagues, board members, partners, supporters

One person can wear several hats. In a small company, the owner may be the decider, the contributor and the finance lead at once. Even so, write each role down. It reminds you which kind of attention each decision needs.

Match the map to the five steps

The partnership process runs through contact, an online meeting, a conversation about rights and goals, a small pilot, and an agreement for a fuller start. For each step, ask which people on your map are involved and what they must do.

StepQuestion for your sidePeople involved
1. ContactIs it all right to approach a partner in Japan at all?Decider
2. Online meetingWho attends, and who can speak for us?Decider, contributor
3. Rights and goalsWhich works are involved, and who holds the rights?Adviser, contributor
4. Small pilotWho gives the time, and who approves the budget?Decider, contributor, finance lead
5. AgreementWho reads the terms, and who signs?Decider, adviser

Notice that the heaviest approvals cluster at steps four and five. You can arrive at those steps with the answers ready, simply because the map reminded you early.

Build your map in fifteen minutes

You need a pen, one sheet of paper or a blank page on screen, and the five steps of the process written across the top. Work alone first, then check the map with one trusted colleague, who will usually add a name you forgot.

  1. List the people. Write every name that could have an opinion about the project. Include the ones you hope will not.
  2. Label each. Mark each as decider, contributor, adviser or observer.
  3. Attach a step. Next to each name, write the first step at which they are needed.
  4. Write the question. For each person, write the one question you need them to answer. Make it a yes-or-no question where possible.
  5. Set a date. Give each question a date, working backwards from the meeting where you need the answer.

The result is a simple table with name, role, step, question and date. Keep it to one page, and share it only with the people who help you run the project.

A filled-in example

Imagine a small music school preparing for one online class with a partner in Japan. The names below are roles, not real people.

RoleKindFirst stepQuestionDate
School directorDecider1May we hold an online meeting and one pilot class?Before the first message
Head vocal teacherContributor2Can you teach or host in the proposed window?Before the meeting
Office managerAdviser4What budget can we set aside, and who pays?When the proposal arrives
Legal adviserAdviser3Does any teaching material need a rights check?Before the rights conversation
Parents' committeeObserver4Nothing; send an update when dates are setAfter the plan is agreed

With five lines the school already knows which approvals to chase first and which can wait. A map for a larger festival or label will have more lines, but the same columns.

What to ask each kind of person

Deciders

Ask for a clear boundary rather than a clear plan. For example: "May we hold up to three conversations with a Japan partner and run one small pilot, without signing anything beyond it?" A boundary is easy to approve, and it keeps the early steps fast.

Contributors

Ask about time and availability. A teacher or musician who is enthusiastic about a project but unavailable in the pilot window is a problem you want to find out about now. Ask them to check their calendar before you propose dates.

Advisers

Ask for a short list of things to confirm, not a full review. For rights, bring a list of the works that might be involved and who holds what. For finance, bring the proposal when it arrives and ask what the payment schedule means for your accounts. For any legal question, the person responsible for such matters at your organization, or your own legal adviser, is the right person to consult.

Observers

Ask nothing, and tell them what is happening. A short note after each milestone keeps goodwill high and prevents the unwelcome surprise of a colleague hearing about the project from someone outside.

A short update note for observers

Keep the note to four lines: what happened since the last update, what comes next and when, whether anything is needed from the reader, and who to contact with questions. For example: "We held our first online meeting this week. Next, we will list the works involved and talk about rights and goals. Nothing is needed from you now. Please ask me if you would like to join a later meeting."

Use the map to avoid common stalls

  • The silent decider. Someone who has not said yes or no is not a yes. Put their name on the map with a date for an answer.
  • The late adviser. A legal or finance review requested at step five can delay everything. Ask for their input at step three, when rights and goals are discussed.
  • The overloaded contributor. If one person appears next to every task, reduce the scope or add a second person.
  • The uninformed observer. A short, regular update costs little and protects the project's support.

The partner's guidance on evaluating a pilot notes that every pilot needs a review with the partner and a decision to continue, change or stop. The same people on your map who approved the pilot will be needed again for that decision, so keep them informed along the way.

Share the map's results with the partner

You do not need to send the map itself to the partner, but you can share what it taught you. Tell the desk who will attend the first online meeting, which decisions need approval on your side and how long those approvals usually take. Mention whether rights questions will involve any outside parties. This information helps the desk plan realistic dates and prepare the right proposal.

It also shows that you take the project seriously. A partner who sees that you know your own decision path can trust that dates will hold and that answers will arrive. That trust is valuable in a relationship built across borders, and it begins with one page of names and questions.

When your map is ready, you can send your first message to the partnership desk and mention who will join the first online meeting.

Contact the Global Music Partnership desk

FAQ

How many people should be on the map?

A small project works well with four to eight names. If the list grows beyond ten, group the observers into a single line.

Do I need approval before the first message?

Check with your decider. A brief yes to contacting a partner and holding an online meeting is a good start.

Should the partner see our stakeholder map?

Not the map itself, but share who will attend and which approvals take time, so the desk can plan realistic dates.