Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Industry Quotes for the website #58

Open
8 tasks
ExperimentsInHonesty opened this issue Oct 20, 2021 · 1 comment
Open
8 tasks

Industry Quotes for the website #58

ExperimentsInHonesty opened this issue Oct 20, 2021 · 1 comment
Labels
p-feature: guidance guidance for how to make guides p-feature: landing page role: Product size: 1pt Can be done in 6 hours or less

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Oct 20, 2021

Overview

We need some quotes to give weight and context to our website so that it can be perceived as authoritative.

Action Items

  • Identify a quote that is illustrates What we are doing, Why we are doing it (Value), How we are doing it (Methods)
  • Paste below with
    • quote
    • Name of person
    • Title of Source
    • location of source information (video link, website link, book/chapter, etc.)
    • where we will probably put it on the site
    • Any context notes needed to understand why this quote is valuable

Resources/Instructions

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Oct 20, 2021

Quote:

Lets' look into some of the invisible stuff we're juggling behind the scenes to operate and communicate effectively as we scale our design system team. We invest in creating methods and systems to multiply our mental models. So our team invests in a disciplines approach to record common processes and shared knowledge. We call these run books, and we add them whenever necessary. They don't have to be perfect, they just have to be helpful and accurate. And documenting this information onwards our team to learn by doing. They simplify training. They help retain and share knowledge. And for me personally, it also demonstrates the importance of strong information architecture. We have to organize and label content effectively so it's easy to find for our teammates.

I know this is a lot of extra documentation on top of the documentation we already have to create for the system, but invest in documenting ways of working so your team can operate efficiently at scale. These will help you scale your knowledge effectively and ensure quality and consistency as different teammates come and go, and also work on different parts of the system.

Name of person: Jennie Yip
Title of Source: Video: Reimagining Atlassian Design System
Location of source information (video link, website link, book/chapter, etc.): https://www.youtube.com/watch?v=_pfyLVXTVSQ at 25:23 - 26:00 26:57 - 27:20
Where we will probably put it on the site: Why and How sections
Context Notes: Atlassian creates guides and run books. We won't be using the entire quote but I provided here so we can talk about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p-feature: guidance guidance for how to make guides p-feature: landing page role: Product size: 1pt Can be done in 6 hours or less
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

1 participant