Where should you start before configuring MapMyStaff?
Choose one simple situation your team already knows. Decide what belongs in the first test, gather only what that situation needs, then verify it before adding the rest.
Start small and expand after the first test
The guide recommends defining a scope, preparing the necessary rules and data, using a representative case, then validating real situations before a gradual launch.
Decide what you are checking now
Choose one concrete situation and limit the first test to what is necessary to understand it.
- 01Choose the situation
Use a situation your team already knows, such as a booking, a field day, or a service area.
- 02Set the scope
Record the functions, territory, people, and language that matter for this first case, plus a target date if one is already known.
- 03Decide what can wait
Leave functions and special cases that do not change this first test for later.
- 04Name who can confirm
Identify the person on the business side who knows this way of working and can confirm the decisions.
Prepare only what this situation needs
Before configuring, gather the decisions, information, and people directly connected to the case you chose.
- 01How your business works
Clarify the services, durations, prices, taxes, areas, availability, absences, promotions, or exceptions that actually change the chosen case.
- 02Necessary data
Prepare and clean only the useful information. Avoid bringing in data that does not serve the test.
- 03Responsibilities
Know who prepares the information, who confirms the expected workflow, and who will use the function.
- 04Test case
Prepare a representative environment or test data set for the situation you want to verify.
Check a real situation before adding complexity
Use a representative case to compare what your team expects with the behaviour actually observed.
- 01Prepare the case
Use the necessary information and a representative test data set.
- 02Check the workflow
Follow the situation from beginning to end with the planned configuration.
- 03Test a less common case
Then add a relevant edge case to check a known exception.
- 04Record differences
Document the decisions, limits, and changes that still need confirmation.
Add the rest once the first workflow is understood
After the essential scenarios are validated, expand the configuration and prepare the launch gradually.
- 01Train the people involved
Prepare training for the roles that will actually use MapMyStaff.
- 02Document decisions
Keep a record of limits and approved changes before launch.
- 03Launch gradually
Start with the validated scope instead of adding every function at once.
- 04Watch the first workflows
Check the first uses and revisit decisions that still need adjustment.