Partner fit
Questions to Ask a Japan Partner About Their Past Projects
Past projects show how a partner plans, communicates and finishes. These friendly questions help you learn their style before the pilot begins.
The short answer: ask your Japan partner to walk you through one or two earlier projects, from the first idea to the final result, and listen for how they plan, share roles, communicate and finish. A handful of friendly, open questions in the first online meeting shows you how the partner works, and it shows them how you work, which is the best foundation for a small pilot.
The Japan partnership desk at global-music-partnership.jp connects labels and music companies, schools and educators, and festival or event organizers abroad with partners in Japan. The path begins with a first contact and an online meeting, then a conversation about rights and goals, then a small pilot. Past projects are a natural topic for the meeting, since they let both sides talk about real experience rather than plans alone.
Why talk about past projects
A plan describes what a team hopes to do, and a past project shows what the team did. When a partner describes an earlier project, you hear how they begin, how they divide tasks, how they handle changes and how they close. You also hear what they are proud of, which tells you what they value. These details are more helpful than a list of titles, and they make the pilot conversation concrete.
The same applies to you. Prepare a short story from your own earlier work so you can share it when the partner asks. A story shows your style, and it gives the partner something real to respond to.
The company behind the desk
The desk is run by AtoNO Records Inc., known in Japanese as Kabushiki Kaisha A-to-Number Records, founded in 1995, with Naoto Tanaka, known as TARNAR, as representative. The company page tells the story of the group and its services under the line BELIEVE YOUR VOICE. In your first meeting, you can ask the team to share the parts of that story that matter to your type of project, and the team can tell you about the projects that suit your goal.
Questions about how the project began
Start with the beginning. A project's first steps reveal how a team thinks.
- How did the project begin, and who proposed it?
- What was the goal in one sentence, and how did you agree on it?
- How did you choose the partners, and what made the fit feel right?
- What did you decide before the work started, and what did you leave open?
Listen for a clear goal and a shared start. A team that can state its goal simply is likely to run a pilot with the same clarity. Listen too for how the partners were chosen, since it shows what the team values in a collaboration.
Questions about roles and communication
Day-to-day habits decide how a pilot feels. Ask about them directly.
| Topic | Question | What to listen for |
|---|---|---|
| Roles | Who did what, and how were tasks divided? | Clear owners and a written role sheet |
| Contact | Who was the main contact on each side? | One lead per side |
| Meetings | How often did you meet, and how did you share notes? | A steady rhythm and written recaps |
| Language | Which languages did you use, and how did you manage them? | A plan for bilingual work |
| Decisions | How did you make decisions when opinions differed? | A shared goal as the tiebreaker |
The answers tell you whether your own habits will fit. If you like weekly check-ins and written recaps, a partner who describes the same routine is a good match. If the partner's routine differs, you can discuss a middle path in the pilot plan.
Questions about rights, credits and results
Rights and credits are written down before work begins, so ask how earlier projects handled them. Questions about results show what the team considers a success.
- How did you decide who held the rights to each work, and where was it recorded?
- How were credits written, and in which languages?
- What did you deliver at the end, and how did you share it?
- What did you learn that changed how you work now?
- If you ran a pilot, what did you review at the end, and what did you decide?
Ask these questions in a spirit of curiosity, and avoid pressing for confidential details. Partners decide what to share, and a general description of their process is enough to see how they work. If your project involves complex rights, include a legal adviser in the conversation, and agree on the details in writing.
Keep the tone light and curious. A question such as "What was the most enjoyable moment of that project?" opens a warm story, and it often reveals more about a team's values than a formal question about process. Follow with "What made that moment possible?" and you will hear about the people, the planning and the habits behind it. Thank the partner for every story, and mention one thing you noticed that you admire.
Adjust the questions to your partner type
The desk describes three kinds of collaboration: labels and music companies, schools and educators, and festival or event organizers. Each has its own typical projects, so add a few questions that fit.
| Partner type | Typical past project | Questions to add |
|---|---|---|
| Label or music company | Co-production, catalog release, joint songwriting | How did you prepare the release? How did you share the catalog? |
| School or educator | Lesson exchange, teacher visit, online class | How did you plan the class? How did students respond? |
| Festival or event organizer | Shared stage, joint show, performance in Japan | How did you plan the running order and technical needs? |
Use the right-hand column as a prompt, and let the conversation follow the partner's stories. A follow-up such as "What would you do differently?" is welcome in every case, and it shows genuine interest.
Taking notes during the meeting
Use a simple note sheet so that stories from the meeting become comparable. Draw four columns: the project, how it started, how the team worked and what came out of it. Add one more line at the bottom for anything that surprised you. After the meeting, read your notes aloud to your own team and ask each person what they heard. Different listeners notice different things, and together they build a fuller picture of the partner.
| Column | Notes to capture |
|---|---|
| Project | Name, type and when it took place |
| Start | Goal, how partners were chosen, what was agreed first |
| Way of working | Roles, meeting rhythm, language plan, decisions |
| Result | What was delivered, how it was reviewed, what was learned |
Turning stories into a pilot plan
The best use of these stories is to shape the pilot. If the partner describes a strong habit, such as a weekly written recap, adopt it. If the partner mentions a challenge, such as scheduling across time zones, plan for it from day one. If you hear a result that you would love to repeat, such as one finished song or one lively class, make it the model for your pilot goal. The aim is one goal, a short period and clear roles, so choose the story that fits those three things best and borrow its shape.
When the pilot plan is drafted, share it with the partner and ask whether it reflects what they described. A plan built from their own experience is easy for them to say yes to, and it shows that you listened.
Share your own stories
The conversation flows in both directions. Prepare two short stories from your own work: one that went smoothly and one that taught you something. Describe the goal, who did what, how you communicated and what you delivered. Keep each story to a minute or two, and finish with what you would repeat. Sharing a lesson with warmth shows maturity, and it tells your partner you are ready for the learning that a pilot brings.
After the meeting, send a short recap that mentions what you learned about each other. Include the questions you would like to explore further, and propose a goal for a pilot that fits what you heard. The desk's next step is a conversation about rights and goals, where you clarify who holds which rights and what each side will do. Your notes from the past-projects conversation are a helpful input for that discussion.
Next step
Write down five questions from this list that matter most to your team and two stories from your own work. Then contact the Japan partnership desk through the form or LINE at global-music-partnership.jp, with your company, country, time zone, goal and preferred language, and bring your questions to the first online meeting.
FAQ
How many past projects should we ask about?
One or two projects described from start to finish are enough to see how a partner works.
Should we prepare our own stories?
Yes. Two short stories, one that went smoothly and one that taught you something, make the conversation balanced.
Does the first meeting happen in English?
The desk works in English and Japanese, and you can choose your preferred language when you make first contact.
What comes after the first meeting?
A conversation about rights and goals, then a small pilot, then an agreement before you expand.