Pilot kickoff
Pilot Kickoff: The First Seven Days After You Agree
The first week sets the rhythm for the whole pilot. Here is a simple seven-day plan that turns an agreement into steady, visible progress.
The short answer: spend the first seven days of a pilot confirming four things (goal, roles, deadline and review method), setting up one shared place for files and messages, and holding a first real working session before the week ends. A week like that gives both teams early proof that the plan works, and it leaves plenty of time for the creative work.
At global-music-partnership.jp, a pilot is a short, time-limited project with one goal, such as a co-written song, an online class or a joint showcase. Before it starts, the two sides agree on the goal, the roles, the deadline and how they will review the result. The first week turns those four agreements into a living routine.
Before day one: the four agreements on one page
Start the week with a single page that states the four agreements in plain words. Your project lead drafts it, the partner's lead confirms it, and both save it in the shared folder.
| Agreement | Write it like this |
|---|---|
| Goal | One sentence that names what will exist at the end |
| Roles | Each person and what they own |
| Deadline | The final date, plus one or two checkpoints in between |
| Review | How and when both sides will look back at the result |
This page is the reference for every decision during the pilot. When someone suggests a new idea, the team asks one question: does it serve the goal? If it does, it joins the plan. If it is a good idea for later, it goes onto a list for the review.
Day 1: say hello and confirm the page
Open with a short message from your lead. Thank the partner, attach the one-page agreement summary and ask for a quick reply that confirms it. Include the contact sheet with each side's lead, a stand-in, time zone and working language. A reply within one working day shows that both leads are ready.
If the pilot involves rights to specific works, restate where those details are recorded. The pilot path places the conversation about who holds which rights before the pilot begins, so on day one your job is only to point to the record and make sure it is saved where everyone can find it.
Day 2 and 3: set up the shared space
Create one shared folder and one message thread. Keep the structure simple, so that people on both sides find things in seconds.
- 01 Plan: the one-page agreements, schedule and contact sheet
- 02 Working files: drafts, demos, lyric sheets, slides
- 03 Final: approved versions only
- 04 Notes: meeting recaps and the decision log
Agree on file names that include the date and a version number, written the same way by everyone. State in the folder's first file which language is used for notes. If your team works in English and the partner works in both English and Japanese, a short line such as "notes in English, with Japanese terms in brackets" avoids confusion.
On day three, work out the meeting calendar. Compare time zones, propose two slots for a weekly check-in and confirm one in writing. Choose a regular day and a regular hour so that both teams build it into their routines. Add the first working session to the calendar at the same time, ideally on day five or six.
Day 4: prepare what the first session needs
The first working session should produce something real, however small. Look at the pilot goal and ask what the first useful step is.
| Pilot type | First real step | Prepare |
|---|---|---|
| Co-writing a song | Listen to reference songs together and choose theme, lyric language and audience | Each person brings their reference songs with a line about each |
| Online class | Draft the outline of the class and the order of activities | A short profile of each group and the questions you hope the class will answer |
| Joint showcase | Sketch the running order and the technical needs | Each side lists its performers, time slots and equipment |
Send the preparation list to the partner on day four, with a clear request and a date. Use a numbered list with no more than five items, since short lists get quick replies.
Day 5 and 6: hold the first working session
Run the session as a real working meeting, with a short agenda and a clear owner for each item. A simple structure keeps it focused.
- Welcome and a quick check of the one-page agreements.
- The main task of the session, such as choosing a theme or outlining a class.
- Decisions made, with a name and a date for each next action.
- A short look at the calendar for the coming week.
Keep notes as the session runs, and read the decisions aloud at the end so both sides hear the same words. Join in English or Japanese according to the plan you made, and give extra time for questions. A little patience in the first session builds trust that carries through the pilot.
If the session reveals a gap
Sometimes the first working session shows that a role is unclear or a schedule is too tight. Treat this as a win: the pilot is small precisely so that such things appear early. Name the gap, agree on a fix and update the one-page agreements. Send the updated page to the partner so that the record stays current.
Day 7: recap and set the rhythm
Close the week with a recap sent by your lead on the same day as the session or the day after. Keep it brief and use a fixed format that you will repeat each week.
| Section | Content |
|---|---|
| Done | What was completed this week |
| Decided | Decisions made, with names |
| Next | The next three actions with owners and dates |
| Questions | Anything that needs an answer before the next check-in |
Ask the partner's lead to reply with corrections or confirmation. By the end of day seven you have a one-page plan, a shared folder, a weekly meeting and a first piece of real work. Those four things are the best possible start for a short pilot, and they make the later review easy to write, because the record is already in place.
Keeping the rhythm after week one
From the second week onward, follow the same pattern: a weekly check-in, a written recap, and a clear list of three actions. Keep an eye on the deadline and the checkpoints, and mention them at the start of each meeting. When the pilot nears its end, schedule the review you agreed on at the start, and prepare a short summary of what was made, what worked and what you would change. The same record will help you decide whether to scale up, pause or close, and, if you scale up, to review conditions, cost, schedule and rights before an agreement is signed.
A sample week at a glance
Here is the whole week on one table, which you can paste into your shared folder and adapt. Adjust the days to suit both time zones; the order matters more than the exact day.
| Day | Main action | Owner | Output |
|---|---|---|---|
| 1 | Send the one-page agreements and contact sheet | Your lead | Partner confirmation |
| 2 | Create the shared folder and message thread | Your lead | Folder structure and naming rule |
| 3 | Fix the weekly meeting and the first session | Both leads | Calendar entries in both time zones |
| 4 | Send preparation requests | Your lead | Numbered list with dates |
| 5 or 6 | Hold the first working session | Creative owners | First real piece of work and decisions |
| 7 | Send the weekly recap | Your lead | Done, decided, next, questions |
Print the table or pin it where the whole team can see it. When each person knows what is expected from them on each day, the week feels light, and the partner sees an organized, friendly team.
Small habits that make the week easier
A few small habits help any cross-border pilot, and they cost almost nothing. Write dates with the month spelled out, such as 14 March, so that nobody mixes up day and month. Give times in both time zones, for example by writing your own city and the partner's city next to the hour. Start each message with the one line that matters most, and place details below it. Keep a shared list of terms for words that are used in both languages, and add to it whenever a new term comes up in a meeting.
Celebrate small steps. When the first working session ends, send a short thank-you that names one thing you enjoyed. In a short pilot, goodwill builds quickly, and a friendly tone in the first week carries the project through busy weeks later on.
Next step
Draft your one-page agreement summary and your shared folder structure before the pilot begins, so day one is smooth. To start a conversation about a pilot, tell the Japan partnership desk your company, country, time zone, goal and preferred language through the form or LINE at global-music-partnership.jp.
FAQ
What should be ready before day one?
The goal, roles, deadline and review method, written on one page and confirmed by both sides.
How often should we meet during a pilot?
A weekly check-in at a fixed time works well, with a short written recap after each meeting.
Which language should the notes use?
Choose one working language for notes and add Japanese terms in brackets where helpful; the desk works in English and Japanese.
What if the first session shows a problem?
Name it, agree on a fix and update the one-page agreement. Early adjustments are the reason pilots are small.