Skip to content

What makes a good or bad designer, developer, sys admin…

Natalie Nagele on the Wildbit Blog:

On the last retreat in April, we asked the entire team to read Ben’s Good/Bad essay. Everyone then spent an hour writing out what they think makes a good or bad developer, designer, QA engineer, etc. We wanted each person to put their expectations down for their teammates. We then regrouped and read them all out loud. We made comments and put together common themes. Finally, each team (designers, developers, QA, success, etc) broke away, and started crafting their own essay on what makes a good/bad _______.

I love this approach to setting job expectations and clarity around what makes a role great. Kudos to the Wildbit team for sharing their documents for the community to review and use.