Failure is scary. But if your product is going to fail, it’s good to know that as soon as possible. Failing fast is the only way you’ll get a chance to pivot, adjust and ultimately create a product that will succeed.
That’s one takeaway from the Tomorrow Toolkit, a 20,000-word, 20-chapter ebook Technical.ly published last year with support from Comcast NBCUniversal. The book shares best practices on starting and building a company from founders across the country. Topics include finding a cofounder (should you find a cofounder?), writing a business plan, securing funding and so much more.
It starts, as all startup stories do, before there is an actual company. In Section A, founders from D.C., Atlanta, Denver and beyond share lessons on what to do before launch.
Here are four key takeaways:
1. Find your people
- As humans, but also as startup founders, we all need support. Figure out what resources are available to you locally, and engage with them. Attend those networking events. Rejoice in talking shop.
2. Use the scientific method
- A company, pre-launch, is a hypothesis. Finding low-stakes ways to test this hypothesis will help you, as discussed above, fail fast and learn from it.
3. To cofounder or not to cofounder?
- It’s not a requirement, but having someone to learn and grow with along the startup process can be a blessing. Think about this when you consider whether you’d like to embark on your venture with a cofounder — those who have gone before also advise testing your relationship with a prospective business partner by working on a smaller project together first.
4. Define the point
- Why are you building this company? What’s your mission? How you go about achieving this mission will likely change in the course of building your business, but the mission itself is unlikely to shift. So put some thought into it — write mission statements and share them with friends and family (that all-important social network!) to get feedback.
Building a successful business is in no way a formula, but there are some basic considerations we can all agree on. Learn those lessons in the Tomorrow Toolkit.
This article is underwritten by Comcast. It was not reviewed by Comcast before publication. Learn more about Technically Creative here.
Before you go...
Please consider supporting Technical.ly to keep our independent journalism strong. Unlike most business-focused media outlets, we don’t have a paywall. Instead, we count on your personal and organizational support.
3 ways to support our work:- Contribute to the Journalism Fund. Charitable giving ensures our information remains free and accessible for residents to discover workforce programs and entrepreneurship pathways. This includes philanthropic grants and individual tax-deductible donations from readers like you.
- Use our Preferred Partners. Our directory of vetted providers offers high-quality recommendations for services our readers need, and each referral supports our journalism.
- Use our services. If you need entrepreneurs and tech leaders to buy your services, are seeking technologists to hire or want more professionals to know about your ecosystem, Technical.ly has the biggest and most engaged audience in the mid-Atlantic. We help companies tell their stories and answer big questions to meet and serve our community.
Join our growing Slack community
Join 5,000 tech professionals and entrepreneurs in our community Slack today!