Once you have a clear picture of what your appathon is going to look like, you move to another significant step: getting the team on board. There are a few aspects to this, including pitching the idea to stakeholders, selling them on that idea, and then getting the participants prepared. In this lesson, we’ll look at everything you need to get your team on board.
Engaging the stakeholders
There are three main phases in getting your team on board:
Before you can move forward with a low-code/no-code appathon, you’ll need to pitch the idea to your colleagues, managers, expert volunteers, and any other stakeholders who are going to be involved in the session. Communication matters and great communication is the best way to get people in engaged. What sort of things can go along with this? A proposed agenda, list of participants, and a value proposition are great places to start.
Once everyone is signed up and aware of what’s going to happen, you’ll need to prepare the prerequisite tasks. For example, if you’re working in SAP AppGyver, make sure the participants have created their accounts and can access the platform, and that they have installed the SAP AppGyver Preview app on their mobile device. You might even consider a small "hello world" type task that can provide a quick intro to the tools.
In this context, it is all about mindset. Hackathons and appathons are meant to be engaging and fun, but it’s also going to be challenging for many participants, especially if this is the first time they’re seeing these tools. Help your participants to get in the right mindset before the session.
Let them know that it’s going to be intense and difficult at times, but that the group is there to support them, and that making mistakes is perfectly fine and completely normal.
What else can you do to get your team on board for your appathon? And what are some big selling points to induce them to participate? Let’s head to the next section and Hear from the Experts.
Preparing participants for the event
Our experts have had plenty of experience in pulling off epic hackathons. Let’s hear some of their thoughts on what the value propositions are for such events, and how you can onboard the team properly.
Here’s a sneak peek of what they’ll share:
"It’s great to participate in such a hackathon because you can really experience on your own how the tool [behaves]. You can see what is possible and what is not possible, and this helps a lot later on [as teams start] adopting the tool."
"Engage the stakeholders very early on. You might want to list who should participate, why they should participate, and then give them enough time. Prepare an agenda of what they’re going to do. And don’t try to do everything by yourself."