MyWorq: employee app for horticulture
Employee app for horticulture — live with thousands of users
An employee app for the horticulture sector, built to lift employee satisfaction, productivity and day-to-day collaboration. I led it as product manager — from mapping what workers and team leaders actually needed, to shaping the roadmap, to rolling it out. The app is now live and used by thousands of workers across horticulture.
I The work
01
The story
bQurius brought me in to lead the product. I spent time on the ground — talking with team leaders and greenhouse workers — to map real needs and pain points rather than assumed ones, and turned that into a roadmap the team could ship against. Over roughly two years, the app grew from concept to a product used daily by thousands, at which point I handed the product role over to the client's own team.
02
Problem
Horticulture is a demanding place to build software for: a seasonal, multilingual, largely deskless workforce.
- High turnover, and skilled people are hard to find
- Complex planning driven by seasonal peaks
- Language barriers with international workers
- No digital tools built for field workers
- Communication gaps between management and the operational floor
03
Solution
- Intuitive interface, available in multiple languages
- Real-time planning and task management
- Direct communication between teams and supervisors
- Gamification to drive day-to-day engagement
- Integration with existing HR and planning systems
04
Way of working
- 🔍 Research — talk to customers to understand needs and pain points
- ✏️ Sketching — sketch what a new feature could look like
- 🎨 Designing — work it into a prototype with a UX/UI designer
- 💻 Building — engineers build the feature into the app
- 🧪 Testing — test the new feature thoroughly
- 🚀 Rollout — ship the update to users
- 🔄 Iterate — analyse data, gather feedback, and start again
II Outcome
05
Role
This is a product-management case. The app itself was built by an external software agency — my job was to own the product: discovery with real users, prioritisation, and steering design and engineering toward what mattered most. In other words: I was accountable for what got built and why, not for writing the code.
06
Status
Live — running in production with thousands of horticulture-sector users. I handed the product role over to the client after roughly two years.