Which tools help teams plan, test, and collaborate on growth-driven design?

The method's improvement cycle has the team plan around a focus metric, build the chosen changes, learn from the results and pass what it learned to marketing, sales and service. The tools here serve three of those steps: the plan and its owners in planning, observation and comparison in learning, and the record in the handoff.

Suppose a company that sells inventory software wants more trial signups from its features page, where the signup form sits at the bottom. The team's idea is to move the form higher.

Asana's project management features are built around tasks that carry an owner and a due date. Projects collect the tasks, and the team can view them as a list, a calendar, a timeline, a Gantt chart or a Kanban board. Asana says its Personal plan covers tasks, owners, due dates and the core views. Its Starter plan adds timelines, Gantt charts, custom fields, forms, rules and custom templates.

In the example, moving the form becomes a task assigned to the designer with a due date, and the developer's build is a second task with a later one. The discussion about where the form should go stays in the comments on the task, where people who join later can read it.

Asana is a general work manager, and nothing about it is specific to growth-driven design. A shared document can also hold the plan, and a small team may prefer it. The choice depends on what the team needs to see. If people keep asking who owns a change or when it's due, a tool built around owners and dates answers that directly.

Microsoft Clarity records visitor sessions and draws heatmaps of clicks, scrolls and drop-offs. Microsoft advertises it as free, with no traffic limits.

In the example, the scroll heatmap shows that few recorded visitors scroll as far as the form. That tells the team where to look, and it leaves the reason open. The form could be too far down. The page above it could also be failing to persuade anyone to try the product. A recording shows what happened on the screen and doesn't establish why. Interviews and sales conversations are ways to ask.

Lean Labs' growth-driven design program reviews page behavior together with form results, CRM lifecycle data and feedback from the sales team. That combination matters in the example. If the CRM is connected to the signup form and records which trials became paying customers, the team can check whether signups from the features page turn into accounts. If few of them do, raising signups there is worth less than it looks. So the CRM and the sales team's notes belong on the tool list too.

Observation gives the team a suspicion, and a controlled comparison tests it. HubSpot's page A/B test is available on Content Hub Professional and Enterprise. It serves two versions of a page at the same URL and sends half the visitors to each. A visitor sees the same version for the length of a session and is assigned again at random in the next one. HubSpot recommends changing one variable at a time.

In the example, the second version has the form near the top and nothing else changed. When the team chooses a winner, the other version becomes a draft. Choosing is the team's job. So decide before the test starts which number you'll compare and how much data you want before you call it.

On WordPress, Nelio A/B Testing's free plan allows one active test and 500 tested pageviews a month. That quota limits how much you can test. It isn't the amount of traffic a question needs. We go further into that setup in growth-driven design on WordPress.

A test on a quiet page can run past the end of the cycle without a clear result. The team can still act on recordings, customer conversations and its own judgment, as long as the record calls a before-and-after comparison what it is.

A 2005 Nielsen Norman Group essay makes the case for using both kinds of evidence. A live comparison measures the outcomes you chose and doesn't explain why people behaved as they did, so the essay recommends pairing it with qualitative observation.

The record belongs where the plan lives. In Asana that can be the task itself. In a shared document it can be a row or a short entry. It should say what changed, what the team saw, what the comparison showed and what was decided. We suggest a format in growth-driven design templates.

The cycle's last step is passing the learning to marketing, sales and service, so the record has to sit somewhere those teams can read it. Suppose the comparison shows more signups for the higher form, and the team picks it. The entry says so, and it adds one open item for the next cycle: check in the CRM whether the extra trials are turning into customers.

Start with what your team already has, and check what your CMS subscription includes before you plan a test. HubSpot's native page test needs Content Hub Professional or Enterprise. On WordPress, a plugin such as Nelio is one route.

Add a tool when you can name a question the current ones can't answer. A team that doesn't know where visitors give up on a page has a use for recordings. A team with a suspected cause and two competing fixes has a use for a comparison.