Miro Business Logic
Aug 2021 – Jun 2022
Content Access and Permissions Management
My role
When I joined Miro, the company was in the hypergrowth state (from 300 to 1,500 in a year), scalable and fast solutions were needed to provide our clients with features they were looking for in a number one online visual collaboration platform on a competitive market.
Business Logic domain is highly interdependent and related to all other product areas such as enterprise, billing, sync or asynchronous collaboration. The key focus area of domain as well as my role in BL: management of access, controlled by complicated matrix of users permissions and roles on different levels of hierarchy.
My responsibilities included:
Regular checkins with stakeholders
Keeping an eye on competitors landscape
Design (and ux bugs) backlog
Fixing existing problems and not creating possible new ones while enabling new features to successfully land in a product.
Board shared with password protection on a mobile device
Discovery
The first initiatives I was involved in were project and board sharing updates. Due to lack of company wide shared information and to get more familiar with the product, I have conducted initial research to document relevant flows, logical dependencies, mental models (in)consistencies. It helped our engineers team to evaluate risks and efforts, PM to prioritise tasks on a timeline, and together we built a roadmap of further product development.
Board sharing flow. Customer Journey Map.
Organisation user list.
Problem
"Karen collaborates frequently with a group of colleagues from her company and wants to get involved into team work faster"
Behind all other problems the major one was that sharing settings were pretty manual and unintuitive for users at scale.
"ACME just started using Miro and wants to onboard the whole company, give all necessary Admin permissions to the people who work in relevant roles"
Goal
Design and introduce a new "User Groups" feature to large enterprise customers
First, I run interviews with admins and managers to learn from our current customers how admins keep their org structure updated and what exactly they want. Properties user group should have. Key learnings: usage of identity providers to sync org members with other platforms, easiest way to CRUD groups of users is to sync it through IdP. Manual groups creation. Nested groups of users would be nice to have but hard to sync. Second, define main user stories we would like to cover.
As a… Enterprise Miro user, I want to:
Invite user groups to projects and boards to collaborate
Mention group of my colleagues on boards and in comments
Be able to notify group members or just mention their presence
See users who belong to the mentioned group
As a… Guest in a corporate account, I want to:
See and contact mentioned users in the group if I have permission
As an… Admin, I want to:
Upload and update my organization members list using IdP
The solution we came up with has to be low cost, simple, and intuitively integrated into an overly complicated settings menu. Final design was developed through iteration and feedback loops.
User groups list. Beta version staging.
Key Deliverables
Journey map that shows all roles on a user group lifecycle
Interactive prototype
Research reports
User test scenario and plan
Specs for next stages of delivery, EAP -> MVP
Groups invited to the account. Instantly given permission to see all boards shared company-wide for group of people.
User group card preview. EAP version.
Main Challenge
The challenging was navigating in uncertainty and chaos in communication with stakeholders, to agree on continuously changing (increasing and decreasing) scope of design work, to prioritize problem space, define which rock of the mountain of problems we're going to climb first.
Now I would rather take more ownership and responsibility in indecisive moments if I could in these circumstances. Dependecies on other people were limiting, but that was an amazing experience to learn from.
