Rolling out WorshipPro so your team actually uses it

New software rarely fails because it lacks features. It fails because everyone was asked to change everything at once, and after three weeks they drift back to the group chat. A slow rollout with one clear reason works better than a big launch. Here's an order that keeps it small.

1. Pick one reason

Say what problem this solves first, in one sentence. "From now on, the song list and the order of service live in one place." That's enough. Don't open with a tour of everything the program can do.

2. Start with two or three people

The leader, the person at the projector and whoever handles the roster. They use it for a couple of weeks before anyone else hears about it (Your first month, week by week). You want them able to answer questions, and you want the first plan your team sees to be a real one.

3. Then the band

Musicians get a benefit straight away: words and chords on their phone, in the right key, for this Sunday. Ask them for one thing only: open the plan in the app.

The easiest way to invite them is at the end of a rehearsal:

1. Before the rehearsal, in Admin → Settings → Members, in the Church link card, click Create link, and set Role for new people to Musician.
2. Click Show QR, and put the code on the screen.
3. Give everyone five minutes to scan it with the phone's regular camera and join. Help anyone who gets stuck, right there.

Leave Require approval on if the link might travel. Otherwise, turn it off so that people join straight away.

4. Then the roster

Only when people are used to seeing the plan. Start with one Sunday, not a month. The request arrives by email with a Respond button, and it works with no account, so nobody has to learn anything in order to say yes.

5. Everything else, one at a time

Band click, the stage display, tablets on stands, Text on phones: each gets its own moment, with a reason. A month between each is not too slow.

What to say

Keep it short and concrete. Something like this:

From this Sunday, the songs and the order of service are in WorshipPro. You'll get a link. Click it, sign in, and open the plan. That's all I need from you for now. If you get stuck, ask me at rehearsal.

And when it's the roster's turn:

You'll get an email asking if you can serve. Tap Accept or Can't make it. If you're away, add your dates in the app, and I won't ask you for those weeks.

What not to require at the start

• Everyone installing the app. The plan is in the browser too, and serving requests work from email. A person with no account can still be on the roster. If they have no email either, you'll have to phone them, as you do now.
• A perfect song library. Tidy it as you go: Tidying the song library.
• Everybody in the directory, with full details. Add people as they start serving.
• Tablets on stands. Paper still works. Let the first keen musician show the others.
• Roles for every case. Leader, Musician and Viewer will cover most of a team. Custom roles can wait for a real need.
• The whole church. Members who don't serve have no reason to join yet.

Do insist on one thing for people with wider access: owners and administrators should turn on 2FA from the beginning.

The moment that decides it

The rollout succeeds when the old way stops. While the song list still goes out in the group chat as well, nobody has a reason to open the app.

So choose a date, and tell the team: "After this Sunday, I'm sending the list only in WorshipPro." When someone asks "what are we singing?", answer with a link to the plan, not the list. It feels a little stiff for two weeks. Then it's normal.

Answers to common pushback

• "I'm not good with apps." Show them one screen on their own phone. Let them tap, and don't take it out of their hand.
• "Another login?" They can sign in with Google, and on iPhone with Apple. They only do it once.
• "What if the internet's down?" Songs and plans are saved on the device, and the computer at the projector works offline.
• "What does it cost?" Today we don't charge. If that changes, we'll let you know well in advance.

How to tell it's working

After a month, look at three things: Are people answering serving requests without being chased? Has the "what are we singing?" message stopped? Does the person at the projector start from the plan, not from a list on paper? Two out of three is a good first month.

What's next

• Your team in WorshipPro: invitations, church link and roles
• Your first month with WorshipPro, week by week