---
robots: noindex, nofollow
tags: process, draft
---
# Big Picture Product Process
The goal of this document is to help develop a shared understanding of the way we think about building the Fluent UI component library. I hope this is just the writing down of some commonly held ideas. The only particularly new idea is the concepts of Projects at the end.

## Overview - Diagram
A high level diagram to indicate how each of the topics elaborated on below fit together.


Diagram Source: [excalidraw-2020313193151.excalidraw](https://gist.github.com/JustSlone/47ed531e3273b5dc5b52d669a64432d5)

## Product Strategy
*Timeframe: 2-5 years*
*Set by Product Team*

Our long term vision. How will we provide value to the business and our customers.

Draft Fluent UI Strategy [contact: mmielke, pagildea]:
1) Fluent UI (as an overaching effort) is our strategy how we simplify the developer story and drive coherence for M365 applications
2) Fluent UI is our cross platform strategy (not writing once running everywhere) but aligning on the control anatomy, design tokens, and style dictionary, leveraging the Fluent Design System
3) Fluent UI is our strategy how we make Microsoft developers (and 3rd party) most efficient to build Web M365 extension and app experiences that leads to productive end users

e.g. Design to code, Easy to use components, Accessibility for free, finely tuned performance

## Product Principles / Manifesto
*Timeframe: durable, ongoing*
*More info: [Roadmap 2020](/zS7XP735R76Si87i7aI2Aw)*

Principles help us make consistent decisions across the Products. They call out what makes us different. They encode a part of our team's culture and how we think about the world.

*Reference:*
- https://svpg.com/the-product-manifesto/
- [A Matter of Principle](https://medium.com/the-year-of-the-looking-glass/a-matter-of-principle-4f5e6ad076bb) - Julie Zhuo
- In response: [Creating useful design principles](https://medium.com/@dustin/thanks-for-writing-the-article-julie-8362fd235ae0) - from Medium

*Examples:*
- [Typescript Design Goals](https://github.com/microsoft/TypeScript/wiki/TypeScript-Design-Goals)
- [Agile Manifesto](http://agilemanifesto.org/principles.html)

## Product Roadmap
*Timeframe: 1 year*

We won't be able to accomplish our Product Strategy overnight, so we can use a Roadmap to help guide us there. The Roadmap is a series of steps taking us from where we are today, to where we want to be as defined in our Strategy.

This document defines the mid-term (1 year) focus. It also gives our partners and stakeholders an idea of what is comming in the future.

Current Roadmap: [Roadmap 2020](/zS7XP735R76Si87i7aI2Aw)

*Reference:*
- https://svpg.com/product-roadmaps/

*Examples:*
- https://github.com/microsoft/vscode/wiki/Roadmap
- https://github.com/microsoft/TypeScript/wiki/Roadmap
- https://github.com/Microsoft/TypeScript/issues/29288

## Quarterly Goals (OKRs)
*Timeframe: 1 Quarter*

A yearly roadmap is still too far in the distance to drive actual execution. Each quarter we pick a few goals to focus on. These goals are motivated and defined by our Roadmap.

*Note: We need to support the OKR process set by Office*

## Projects
*Timeframe: 1-6 weeks (maybe 1-3 weeks?)*
*More info: [Shaping a Project](/GAUYjmVZSNibiTOhxOiQ_w)*

In order to accomplish our quarterly goals, we do need to do actual work. We organize our work using Projects. Projects start with a problem to be solved. They include the scoping and tasks required to make signifcant progress in solving, time boxed to a specific amount of time (1-6 weeks).

*Note: We need to support the sprint process set by Teams*