Growth Experiments is a complete platform to track ideas, hypotheses and results.
One of the biggest challenges of their job is accurately scoping work, and being able to consistently and predictably deliver results to clients within the promised timeline. How do you measure your productivity at work — with lead time, cycle time, takt time, or something else altogether? Here’s what those all mean, and how to use each to your advantage.
With the outbreak of COVID-19, organizations all over the world are forced to ask their employees to work from home. It’s likely that you haven’t worked with a completely distributed team, let alone manage one. For testing teams, who usually share an office, this brings a new set of challenges-How to monitor your testing teams’ efficiency when you can’t supervise them directly? How to keep a track of tasks of your distributed testing teams? According to Julie Wilson, founder of the Institute for Future Learning, “Managing a virtual team requires managers to double down on the fundamentals of good management, including establishing clear goals, running great meetings, communicating clearly, and leveraging team members’ individual and collective strengths.” Even though Wilson’s points are true, it is still a tremendous challenge to make the switch to manage distributed testing teams. This article will share 11 tips to help you make a switch to a completely distributed testing teams.
Congrats! A new growth hacking client! The moment has arrived; you have a new client. You feel a nervous excitement rushing through you, a new playground to explore and enjoy but also a new challenge. Unless you’ve sold the project yourself and not within an agency, you usually have no idea what to expect. So let's talk about how you should kick-off this new chapter...
<p>Growth teams are there to act in all stages of the growth hacking funnel. That means running experiments that can influence key business levers and having ever-changing activities to test new ideas. Teams can't get involved with all kinds of tests and requests. Instead, they must prioritize what experiments can bring the greatest benefit for the business at any given time. To help teams prioritize what experiments will be run next, and get organized to bring results that will validate ideas as quickly as possible, teams need growth sprints. That is a ritual moment that can be held weekly to get the team on the same page on what tests will be run next, how the idea will be validated, and set tasks and responsibilities. This is the space for sharing how teams organize their growth sprints, how they prioritize what ideas will be tested next, e what metrics teams set to validate their growth ideas.</p>