Summary:
1. There are different areas of use cases
2. Since you can't implement everything at once, it makes sense to define prioritized use cases
3. Within these, specific solutions and associated use case goals are defined, which should be measured four weeks after the rollout
4. The examples below should help you define your use case goals.
Use Cases Goals
There are several use cases which can be supported by Beekeeper:
- Employee Referrals
- Training
- Company News and Events
- Shift Availability
- Employee Onboarding & Offboarding
- Health and Safety
- Checklists
- Employee Requests
- Continuous Improvement
- Secure, 2-Way-Communication
- Employee Engagement
- Employee Recognition
- Access to Documents & Tools
- HR Benefits & Information
- Policy Updates & Confirmation
- Digital Signage
- Metrics & Reports
Of course, the idea is to use the full potential of Beekeeper. But since you can't do everything at once, it's a good idea to select three to four use cases that are most important to you so we can focus on those use cases for the first rollout phase. In this regard we speak of prioritized use cases. Within these use cases, you can then define specific solutions and associated use case goals. We recommend you measure these four weeks after the initial rollout.
Here a few examples:
Use Case | Beekeeper Solution | Use Case Goal |
Health and Safety | Report near misses via a form and post the learnings anonymously in the Safety stream. |
Quality: Form, workflow and stream are set up and map the process. Quantity: At least 2 near misses were reported via Beekeeper in the first 4 weeks after rollout. |
Health and Safety | Promote safety awareness via campaign and make safety rules available via the document library. |
Quality: Security rules are uploaded to the appropriate documents folder with the correct permissions. Quantity: 1 campaign has been sent, and confirmed by at least 60% of all activated users. |
Employee Requests | Submitting holiday requests via one form incl. approval process. |
Quality: Form and workflow are set up and map the process. Quantity: At least 8 holiday requests were submitted via Beekeeper in the first 4 weeks after the rollout. |
Employee Onboarding & Offboarding | Automated support of the onboarding process of new employees through an onboarding workflow incl. the introduction of the new employee in a post, the availability of the most important company documents and the measurement of the onboarding experience via a form. |
Quality: Workflow is set up and maps the process. Company documents are uploaded to the appropriate folder with the correct permissions. Stream incl. highlighted label "NewEmployees" is set up. Quality measurement form is set up. Quantity: At least 2 new employees have completed the onboarding workflow in the first 4 weeks after the rollout, introduced themselves (without a reminder) in a post and rated the onboarding experience with at least 7 out of 10. |
Employee Onboarding & Offboarding | Institutionalized monthly communication of departures via the company stream. |
Quality: Main stream is up, highlighted label "Personnel" is added and details regarding design and content of monthly leavers posts are defined. Quantity: First leavers post has been posted and has at least 5 appreciative comments in the first 4 weeks after rollout. |
For now, you don't have to do anything. Use case goals can only be set after solutions have been brainstormed and prioritized. We will come back to this in the article Setting Use Case Goals
Previous Page Back to Homepage
Comments
0 comments
Please sign in to leave a comment.