GovrnGovrn is an online platform to improve board meetings and management. It equips the board with the tools necessary to make informed decisions quickly and efficiently. The platform fosters collaboration, ensures compliance, and offers a strategic overview of the business, thereby enabling smarter business decisions for sustained growth and success.
The 2 ambitious founders of Govrn came to us to help design the idea they had to improve board meetings and connect board members to their companies. They had performed over 100 interviews and knew exactly what to improve, they just didn’t know how.
Today, board members of companies are overwhelmed with emails on decisions to make. Govrn wanted to create an effortless way for board members to securely communicate and make informed decisions through a digital platform.
01 / Step
Stakeholders had different vision on the right priorities
02 / Step
We started cutting and pasting screenshots from our favourite search, documentation, and productivity tools we created the first tangible concept.
03 / Step
After 10+ iterations of the wireframes, we derived a clickable prototype of how the app should work. We worked with a mobile-first approach, which forced us to keep the interface simple.
04 / Step
We went to potential users and asked their feedback. We learned that the voting functionality and the calendar concept were unclear at that point. Build fast, learn fast!
After that first validation through research, we dove headfirst into the MVP creation. We deployed 3 tracks at the same time, pretty challenging to keep everything smoothly coordinated, but we managed!
01 / Focus
We conducted a detailed analysis of all functionality and documented it with Feature Passports where the why, the how and the success metrics are captured.
02 / Focus
We designed a high-fidelity HTML version of the user interface. Patterns were documented for swift implementation.
We released the software internally first to generate a lot of feedback. We organized and structured the feedback, so bugs were identified quickly and new ideas were logged for a later stage. Happy beta users were onboarded not long after that.
FlexmailNext case study
After 12 years of development-driven design, Flexmail’s product needed a fresh start. It was not only hard to use but also hard to cut in legacy features and the linked client expectations. How we managed to help them?