Learning path: Support Channels — Learning path

Previous: Submitting Feature Requests to WorkWeek

Next: Return to WorkWeek Academy to choose another module.

As WorkWeek has grown, so has our approach to developing new features. In our early days, we focused on rapidly building solutions to help our customers succeed. Now that we’ve reached a place where WorkWeek enables that success, we’re ready to scale—bringing our customers along on that journey.

The Feature Development Journey

Here’s a closer look at the journey a feature request takes, from initial idea to full release:

1. Alignment and Feasibility Check

• Every feature request goes through an initial review by our product and technical teams. This stage ensures that the proposed feature aligns with WorkWeek’s mission to empower the blue-collar workforce of South Africa and meets our broader strategic goals.
• Our teams assess the technical feasibility, resource needs, and potential impact on the WorkWeek platform. Only if a feature request meets these criteria does it move forward.

2. Ideation and Planning

• Once aligned, the feature enters an ideation and planning phase. Here, we brainstorm and map out the feature’s core logic and structure. The goal is to build a plan that’s clear, detailed, and resilient, so by the time we’re ready to start development, every aspect is thoroughly considered.
• This phase is all about making the feature “bulletproof.” We focus on ensuring the design will meet both immediate needs and long-term goals, creating something our customers will love to use.

3. Development and Testing

• After planning, the feature moves into development. Our technical team begins building based on the refined plan, with each element carefully crafted to deliver a reliable, effective solution.
• Once the initial build is complete, we invite a test group of customers to try out the feature. This stage is essential for gathering honest feedback about what’s working well and what might need adjustments.
• If you are interested in joining this test group, please contact Megan, our Customer Success Manager, to request to opt in.
• Based on feedback, the feature often goes back into development for refinement to make sure it’s fully polished before a wider release.

4. Final Release

• When the feature is thoroughly tested and refined, we’re ready to launch! We make an exciting announcement to our customer community, giving everyone access to the new feature along with guidance on how to use it.

By taking a more structured and thorough approach to feature development, we aim to release features that are thoughtful, impactful, and aligned with the needs of our customers. Thank you for your valuable feedback and for being part of WorkWeek’s journey to build a platform that truly supports South Africa’s working community.

←Previous Page: Submitting Feature Requests to WorkWeek

WorkWeek Academy

• Browse the full Academy topic index