Skip to content

Commit

Permalink
Some text tweaks for the motivation file, done as I was reading it (#16)
Browse files Browse the repository at this point in the history
Co-authored-by: Mark MacKay <[email protected]>
  • Loading branch information
methodofaction and Mark MacKay authored Apr 3, 2024
1 parent 1238cd9 commit 2eccf64
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/Motivation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

**Context and problem:** How did we get here?

- Our current product has a huge surface area. Designers have created ad-hoc components and components to solve their problem at hand, without much consideration of how it affects the platform as a whole.
- Our current product has a huge surface area. Designers have created ad-hoc components to solve the problem at hand, without much consideration of how it affects the platform as a whole.
- This has created a never-ending series of bugs, inconsistencies and poor user experience for everyone involved (customers, designers, developers).
- Our product feels slow, chaotic, inconsistent and disconnected.

Expand All @@ -26,11 +26,11 @@ It’s time to do something about it!
What is the scope?

- UI Foundations (e.g. Tailwind UI, [Shadcn/UI](https://ui.shadcn.com/)) — 100%
- Abstractions (e.g. data collections) — 80%20%
- Abstractions (e.g. data collections) — 80%/20%
- Rendering (list, table, grid, etc…)
- Filerting
- Filterting
- Loading
- Navigation and Information Arquitecture
- Navigation and Information Architecture
- Access points
- UX metaphors (e.g. My stuff vs. My company)

Expand All @@ -42,8 +42,8 @@ What is the scope?
2. Define the core foundations, abstractions and navigation that solve most of the current use-cases (aiming for 80%)
3. Gradually share and involve PDs and FE to redesign (or fit) their current product into the new foundation.
- Work with them to find edge cases and things that don’t fit.
- Iterate until we get 80% of the use-cases covered
- Seriously question the remaining 20% and create ad-hoc components for those who bring a lot of value to the users and the business.
- Iterate until we get 80% of the use-cases covered.
- Seriously question the remaining 20%, then create ad-hoc components for valuable use cases for users and businesses.
4. Adoption and deployment: TBD

# Resources
Expand Down

0 comments on commit 2eccf64

Please sign in to comment.