After experimenting with many collaboration environments, our company decided to centralize all workflows into a single tool, GitHub, supplemented by a new product, ZenHub. Centralizing onto one platform has given us much better focus and transparency; we're sharing our journey to help others achieve similar efficiency.
The journey begins
In the earliest days of our company, we spent quite some time trying out different products and processes. During our search for the perfect workflow we looked at Asana, Pivotal Tracker, Trello, even Basecamp, Google Docs, the dreaded JIRA, and plain old email.
To focus our search, we employed the same decision-making framework as we do when building products. We defined a series of axioms to focus and guide us in the midst of making difficult decisions.
To guide the process of improving our workflow and toolset, we established three initial axioms:
- Working asynchronously is essential for a global team: Most of our team is based in Vancouver, Canada, but we have had folks working remotely from Italy, France, China, and Brazil as well as throughout the rest of the U.S. and Canada (often before moving to Vancouver). This means the tools we use have to be used by everyone, all the time, or else people start feeling - and being - left out.
- Empowering leaders, minimizing meetings, and minimizing management leads to higher-quality results: It was always surprising to us that companies hunted for the best talent and immediately began stifling them with rules and regulations. We wanted a project management tool that let us cut down on unnecessary meetings and paperwork while at the same time increasing transparency and collaboration.
- Using good products makes us build them better: We hold the tools we use to a high standard, believing that a high-quality product starts with high-quality building blocks. For product management, we wanted something lightweight and agile because we wanted to be pushing our system's limits, not the other way around. We build certain values into the products we create: it would be counter-productive and hypocritical not to demand them from the products we use in the process.
Back where we started
Technology is truly at its best when it simply disappears. We think the same is true of process. We struggled with the tools we evaluated because at each turn they seemed to be adding to our workload, not reducing it. Every tool created new queues for us to check, entries needing constant updating, tasks to be assigned and priorities to be colorfully sprinkled throughout.
It was a full-time job babysitting every system. Our product team spent more time curating how the tasks looked on screen, making sure meta information was complete and assignments were made correctly, than actually Building Things, which is what we're all here to do.
From one of our heroes:
Our trust is in people rather than process.
- Warren Buffet
We also quickly realized that the cost of enforcing adoption of a new tool or product is very high. We decided to adopt a fourth axiom, one that runs counter to the tool-happy culture we've grown accustomed to in our personal lives:
- Minimizing the absolute number of products we use is a Good Thing: Additional accounts increase complexity, process, and overhead in many unpleasant ways ⇒ BAD FOR STARTUP.
Using GitHub for everything
During this process we realized something surprising. As product-people and early-adopters, every member of our team is naturally very aggressive: trying new tools, experimenting constantly, and hacking every problem they face. However, as a team we are quite conservative: we prize simplicity, reliability, and an elusive quality we’ve termed “getting-out-of-the-way-ability” in the tools we use.
So we did what we should have done in the first place, and looked with fresh eyes at the place where a majority of our team lives, day in and day out: GitHub.
GitHub is the most popular version control system for software developers, beloved by 7M people around the world. That said, it's far from perfect and many team members (especially non-coding ones) were doubtful it could work as a strategic tool.
Everyone agreed we needed a solution that worked for the entire team: no more silos! Someone suggested: “We could just build what we need and use the browser to inject it in GitHub’s interface.” And that’s when ZenHub was first conceived.
ZenHub is a powerful extension that adds key collaboration and project management features to GitHub, including kanban-style Boards, advanced file uploads, social features, and important shortcuts. To read more about ZenHub's features, check out our other blog post: Supercharge GitHub Workflows: Introducing ZenHub or give ZenHub a try by visiting the Chrome Web Store.
Otherwise, keep reading!
GitHub with ZenHub: biggest wins
Today we use GitHub with ZenHub for every single company workflow: Hiring/HR, Sales/CRM, Support, and internal communications, as well as actual software development. Here are some of our biggest wins.
ZenHub for GitHub makes radical company-wide transparency manageable.
The biggest win from this for us has been in our recruiting/hiring workflow. In a distributed hierarchy that assigns high responsibility to all individuals, the single most important process is finding, attracting, and vetting new team members. ZenHub allows us to bring our hiring process into GitHub, such that the whole team can be involved in all aspects of the hiring process without being distracted and interrupted.
This is a snapshot of a hypothetical hiring repo:
More critical than individual features, ZenHub for GitHub focuses our entire team's efforts in a single, robust tool. Those of you who 'get' productivity understand that tools are only as good as how well they're used – by centralizing every one of our company's workflows onto GitHub, we reduce the mental overhead of juggling multiple solutions and can focus on getting our work done.
As the number of developers multiplies and the cost of starting a company plummets, developers are increasingly the brains as well as the brawns behind potentially world-changing ideas. Given the ease of "scratching one’s own itch", it's no surprise that many developers' brains latch onto developer-centric ideas, making the "B2D" market one of the most competitive in history.
Somewhat in contrast with this intense competition, B2D has given rise to a surprisingly cohesive, collaborative, and altruistic community. The teams and companies using ZenHub during our beta period have been a pleasure to serve – and seeing what they build using ZenHub feels amazing.
Jump on the ZenHub bandwagon
We'd love for you to join us. Among the 10,000+ teams and individuals using ZenHub today, we count open source darlings like Basho and Ghost; enterprise teams at Microsoft, NBC News, and Sony; consumer-facing companies like iFit and Craft Coffee; and many other exciting partners.
What will you build with ZenHub?