Lessons from One Week | One Tool – Part 3, Serendipity

Over the past few months, several people—including several participants themselves—have asked me how we chose the One Week | One Tool crew. We had about 50 applicants. Nearly all of them were perfectly qualified to attend. This made the selection process exceedingly difficult. I have no doubt we could have ended up with another group of twelve and been equally successful. Indeed, I have often joked that with the applicant pool we got we could easily have done "Three Weeks | Three Tools."

In the end, the uniformly high quality of our applicant pool meant we had to make our choices on largely subjective criteria. Who showed the most enthusiasm? Who showed the most willingness to collaborate? Who seemed open minded? Whose writing style showed clarity of thought and energy? Who seemed like the hardest workers? Who seemed eager to learn? Whose seemed like a quick study?

One important thing to note is that we didn’t pick for particular technical skills. Of course we wanted a good mix: a team full of UI specialists or outreach experts wouldn’t have worked. But we didn’t select for PHP, Ruby, Java, TEI, or any other technology. We assumed that if we picked good people with a range of skills, even if those skills were all over the map, we’d end up with something interesting. I think we have.

As it turns out, we have ended up with something even more interesting because of that diversity of skills. Boone said something very telling at the bar on Thursday night: Anthologize probably couldn’t have been built without One Week | One Tool. A single shop wouldn’t have had the necessary range of skills to do it. I know CHNM couldn’t have done it alone. Sure, we have the PHP and JavaScript chops (although not the intimate knowledge of WordPress Boone brought to the table). But we certainly don’t have deep knowledge of TEI and XSLT the team needed to produce Anthologize’s rich, clean outputs. Nor, I suspect, would we even have hit upon TEI as a solution to that particular problem.

There are lessons here for hiring. Pick the smartest people. The best writers. The hardest workers. Pick people with proven track records of working well in teams. People with lots of energy. People who approach heavy workloads with clear thinking and good humor. People who’ve shown aptitude for picking up new technical skills on their own.

These people may not know what you need them to know on Day 1. But they will work hard to learn it. They’ll also bring a host of additional skills you didn’t think you needed, but will be happy to have once they’re there. Having these additional skills on tap may even let you take your work in directions you couldn’t have otherwise imagined.

#oneweek #buildsomething

Leave a Reply

Your email address will not be published. Required fields are marked *