Don't release code without auditing it. A lot of hacks can happen if you put code into production without doing a proper audit first. Avoid this mistake, and prioritize security - before the latest release, 1inch had 10 audits to ensure safety.
2. Find the right contributors
In a DAO, people have shared access to the company's assets, so make sure you share your work with the right people. If somebody abuses the network for their personal gain, it's time to say goodbye to them.
3. Align your teams
It's important to give your teams autonomy, but make sure they still remain in sync with each other. Agree on a global strategic direction to work towards, keep teams aligned, and encourage them to help each other if needed.
Want to learn more about starting a successful DAO?
Check out the full interview through the link below!
The secret of building well-aligned teams is establishing the right hiring strategy. Technical knowledge is important, but focus on finding culturally aligned people who are deeply interested in their field.
2. Keep your teams aligned
When you have teams all around the world, you have to find the right balance between autonomy and alignment. Some practices must be standardized among teams so that you're able to run cross-functional programs.
As an EM, you talk to ICs, leads and the technical director regularly. Make sure you share helpful information with them while also creating a reporting structure where people can talk about their problems confidentially.
2. Coach engineers in their career development
Encourage engineers to evaluate their growth, to pinpoint areas to improve and to ask for help from their lead or seniors on the team. Have career development discussions with them, and discuss the expectations of the next level.
When engineers work on a piece of code, they don't see how it contributes to North Star goals. OKRs help them see the bigger picture, so they'll value their own contribution more.
2. Customize OKRs
An OKR performance management system works best if you tailor it to your team's needs. Be patient when you introduce OKRs, have discussions to see what works and what needs to be changed, and welcome questions and suggestions from everyone.
Cross-functional collaboration works best if you hire well-rounded people who can think outside of their assigned roles. Product managers may have engineering ideas, just like engineers can come up with great product ideas.
2. Encourage empathy sessions
Cross-functional collaboration can cause frustration when people don't see the value of other functions. Hold empathy sessions where cross-functional partners explain what's challenging about their role. They'll appreciate each other's work more.
Do not limit agile to engineering. When your entire organization adapts to the agile philosophies, you can react to changes easier and faster.
2. Strive for "pretty good"
As an agile organization, you’re constantly iterating your product. This means you always leave room for improvement. So, don't try to make everything perfect the first try - strive for "pretty good" and keep iterating!
The number one trait of high-performance teams is psychological safety. If you can establish that within your company, it's easier for everyone to work together and build a high quality engineering product.
2. Evaluate objectively
It's hard to pinpoint what's going wrong in your company. Reflecting on how your teams operate, why they follow certain rituals and how they interact with each other is a good way to start.