teams   6112

« earlier    

Driving design system adoption (UX Collective)
Maya King из REI рассказывает о построении команды дизайн-системы Cedar и выпуске её новой версии. Она показала процесс работы над компонентом и идеальный сценарий внедрения в продуктовую команду. Кстати, их консультировал Nathan Curtis.
UX  design+systems  teams  management  case  issue  adoption 
3 days ago by jvetrau
Design Your Team (Dropbox Design)
Jennifer Brook из Dropbox опубликовала небольшой фреймворк по определению общих ценностей дизайн-команды. Скачать инструкцию (https://assets.dropbox.com/documents/en-us/team_values_toolkit/Color/team_toolkit_sheets_c.pdf) и карточки (https://assets.dropbox.com/documents/en-us/team_values_toolkit/Color/team_toolkit_cards_c.pdf).
UX  teams  management  culture  issue  framework 
6 days ago by jvetrau
More than coders
Lately, the compiler team has been changing up the way that we work. Our goal is to make it easier for people to track what we are doing and – hopefully – ge...
process  management  teams 
6 days ago by nanoxd
Sprout Social Design — Seek Simple (Medium)
Блог дизайн-команды Sprout Social.
UX  company  teams  blogs  articles 
8 days ago by jvetrau
Rage Against the Codebase: Programmers and Negativity
Negativity plays an important role in programming. It’s embedded into our culture at various levels as a way to share learnings and war stories
teams 
9 days ago by pks
IceWarp Cloud Pricing
Clear pricing with no hidden fees. The more you use, the cheaper it is.
email  hosting  team  teams 
11 days ago by iaeon
Using 6 Page and 2 Page Documents To Make Organizational Decisions
Ian Nowland has written up the Amazon 6-pager strategy:
A challenge of organizations is the aggregation of local information to a point where a globally optimal decision can be made in a way all stakeholders have seen their feedback heard and so can “disagree and commit" on the result. This document describes the “6 pager” and “2 pager” document and review meeting process, as a mechanism to address this challenge, as practiced by the document’s author in his time in the EC2 team at Amazon, and then at Two Sigma.

[...] The major variant I have also seen is 2 pages with 30 minute review; when the decision is smaller in terms of stakeholders, options or impact. That being said, there is nothing magical about 2 pages, i.e., a 3 page document is fine, it just should be expected to take more than 30 minutes to review.
amazon  business  decisions  teams  documents  planning 
13 days ago by jm
UX-стратегия. Часть 5 — Дизайн с выхлопом - Юрий Ветров об интерфейсах
как организоваться по работе надо продуктом (ценность бизнесу)
- как найти проблемы продукта
- понять решения
- оценить что проблема решена
metrics  ux  Strategy  teams  KPI  jobs-to-be-done 
13 days ago by akimkin

« earlier    

related tags

&  a  admin  adoption  advertising  agile  airbnb  alerts  amazon  among  and  antonio  any  app  architecture  articles  automation  automattic  best_practices  bien  billgates  blogs  book  books  bots  brainstorming  brand  brown  business  capsule  career  careers  case  cfl  chat  chatbots  chelseatroy  christina  cios  citrix  collaboration  collection  communication  company  comparison  concurrency  config  coo  cool  corporate  creativity  culture  data-science  decisions  defense:  delivers  design+systems  design  designsystem  developing  development  digitalworkplace  disagreement  disruption  distributed  documentation  documents  dutch  email  engagement  engineering-management  engineering  ergonomics  european  feature  feedback  for  framework  friends  google  guild  haglöfs  happy  him  hosting  howto  hr  iconic  ideas  ifttt  in  innovation  intelligence  interested  intuit  irish  isaac_newton  issue  it  it’  james  jobs-to-be-done  johnny  kpi  leader  leadership  leadership_skills  leadership_styles  leading  league  lebron  let  lines  lisp  ma.tt  makeist  management  manager  mangement  manziel  markdown  mentors  message  messaging  metrics  microsoft  mobile  myths  new  notification  of  office  okrs  on  open-plan  opportunities  organisation  organization  out  pane  password  pay_attention  people  performance  personality_types  pinned  plac  planning  pocket  prioritizing  process  product-design  product  productivity  productmanagement  profile  programming  prometheus  psychologicalsafety  psychology  python  qos  raiders  recruiting  redskins  reference  released  remote  safe  scale  scaling  scottish  setup  showcasing  sign  singling  six-piece  skill+knowledge  skills  slack  smalltalk  snapchat  software  solitude  solutions  standards  startups  stop  strategy  system  t20  talent  team  team_management  teamwork  tech  test  their  to  tool  toolkit  tools  training  transformation  true_colores  true_colors  très  tuckman  up  user_experience  userexperience  ux  uxteams  values  voip  with  wmde  wodtke  won't  work  working  workplace  workplaces  ‘come 

Copy this bookmark:



description:


tags: