4 ms·

I'm sure I'm not the only one in the audience interested in more details about how the specific team you may be talking about was organized to come together, op

• juancn 4y ago
  It would take a book to go over it. In the early stages is all about hiring. Getting the right people, minimal structure and let them do what they're best at with a few key leaders with a strong vision. As you grow, you need to build the leadership structure, true believers that let the help people grow. That's the main part, leaders main concern should be people. You need a structure that trusts and empowers employees. If you did the hiring in the first phase right, some of those will rise to lead (maybe as proper managers or as tech leads, architects, lead designers, etc.) Usually, at first you build structure for product and engineering, and maybe place a few UX/Designers as cross functional roles, with little structure, to help all teams build coherent UI. Eventually they grow into their own org and are involved in product driven features in the early stages. Doing mocks, running usability labs, etc. With other functions, such as accessibility and i18n (even security) the same happens, as the org can accommodate them these structures start gaining size and their own internal structure. As the team grows into the hundreds process appears, but is should always be more of a helper than a straightjacket.