Page Comparison

Gabe

• Should the 3 of us meet or sync more regularly for some reason?

  • We should be syncing as leads at least every couple of weeks or monthly to keep Paragon on the rails

  • How do we grow our capabilities?

• What do you need to sync or stay aligned on?

  • Deciding what we will build, what needs updates, prioritizing design efforts, organizing technical work around the priorities

  • Think about Paragon as a product with customers, adoption, tech help, roadmap, regular evangelizing, could alter ho we think about paragon

  • Who are the customers, how are we documenting, when do we need to talk to developers. What is paragon doing well or not doing well.

  • Let’s act like a real product group, even though we are part time and limited in resources

  • What is our current paragon workforce?

    • Design, engineering?

    • Lots of blended? Not the right answer…

      • it does offer augmenting capacity

      • long its not a good solution bc we don’t have enough in house resources

    • front end and paragon support groups spinning up

      • where does tech lead go after that? take anew look at governance models

  • Front end can sometimes fall short, product thinking behind paragon can help drive it better

  • Theme demos! Visibility

  • Any time you use paragon, is there a way to make those successes reflect back on paragon

  • What are our measures of success that we can celebrate over time

  • Health + does it exist?

  • Arbiters of quality?

Ben

• How do we control who should be able to be the final PR approver for Paragon PRs? What are our criteria?

• How to we ensure all paragon components go through our design and review processes?

• What do we do about issues with PRs that have merged, but were not caught because of missed review?