"By failing to prepare, you are preparing to fail." – Benjamin Franklin
Moveworks customers are most successful launching new capabilities when they have a solid plan in place. When clear plans aren't made, critical details are missed which cause projects to be delayed by months at a time. In some cases, projects can be scrapped altogether.
We've aggregated some of the best practices they follow so that you too can be successful.
Every successful use case starts with an impactful idea. Building new capabilities consumes internal time & resources. Showing business value is the best way to ensure your integration comes to life.
When you demonstrate business value, it creates new opportunities. Our customers have gotten the following benefits:
Security reviews - Bringing together new tools often requires a security review to make sure these business systems are allowed to interact. With clear value, you can expedite security reviews or get provisional permission to enable capabilities before thorough systems are fully vetted.
Additional resourcing - New capabilities thrive off domain expertise from other teams. For example, your endpoint monitoring team will know what types of application crashes are most problematic and how to avoid them. Or your hardware asset management team might know exactly how to use the APIs for their refreshment management system. You can rally their help with clear value.
Prioritization - Escape KTLO. The line between important and urgent is thin. Demonstrating that each week the business is missing out on value is a great way to climb above activities like data migrations, software upgrades, and more.
See the Business Value section of our worksheet for tips on establish business value. Some of our mature customers have converted this worksheet into an intake form for othe employees to fill out.
Sending messages through Moveworks is all about improving the employee experience and driving them to take action. You should have a clear insight into what you want your employees to do when they receive their message.
Find ongoing problems - It makes sense to automate something that is ongoing. If you're trying to communicate a one-time migration, you may want to consider our solution for Employee Communications, where non-technical stakeholders can send one-off campaigns.
Keep stakeholders on the same page - The most successful teams are on the same page. Without aligning all stakeholders on the final user experience, you end up with scope-creep. A 2-week project can spiral into 2-month projects unless clear expectations are set up front.
Write out what you want your employees to do after receiving a message. Your customer success team can help create mockups of your use case.
Our API lets you send a message to any list of recipients.
string [ 1 .. 10000 ] characters
Message to be sent, formatted in Moveworks' version of HTML
Array of strings [ 1 .. 500 ] items
Email addresses of the employees to send the message to
Successful projects map out where all the data lives in order to get the approximate architecture correctly.
Make sure you can answer the following requestions
- Can you figure out who should receive the message? How do you get their email?
- Is there data (e.g. laptop models, error codes, dates), that you need to render in the message? Where does that data live?