Choose Your Own AI Adventure: Bottom-Up Tool Selection Beats Top-Down Mandates

Adopt bottom‑up tooling: let teams pick AI tools, then spread proven stacks through organic sharing and light governance.

Sep 29, 2025 0m 29s

James LePage

Expert Insights

James LePage emphasizes the importance of bottom-up tool selection in AI-assisted software development, urging organizations to consider the effectiveness of providing flexibility to developers in choosing their tools.

James reinforces that Automattic's unique approach, which allows developers to expense any tool they want, eventually leads to the sharing of effective systems and tools among developers, thereby creating a diverse and effective collective toolkit.

Listen to James as he shares:

Why implementing a free-choice approach towards tool selection can facilitate a more effective workflow.
How tool sovereignty promotes an atmosphere of resourcefulness and sharing among developers.
The potential impact on the software's quality when developers use tools they truly believe in and understand intimately.
The indirect role of tool-driven synergy in fostering a more productive and satisfied software development team.

I think automatic's a unique company... When you come to automatic, you're not given kind of this pre-collection of tools that you must use. If everybody here can expense whatever tool they want, so they choose what works for them, they build their stack... everybody kind of builds their own systems that they truly are effective with, and then they share it and they're like, Hey, I use Cursor to do this, and then I pass it off to cloud code, and then I pass it off to V zero.

— James LePage, Director of Engineering AI, Automattic

THE NEW DEFAULT angle

Here’s how to effectively implement tool autonomy and collaboration in an AI-assisted development environment:

• Foster tool autonomy: Allow developers to use and experiment with the tools they find most effective for their work.

• Facilitate an environment where developers can share the tools and systems they find effective.

• Evolve with trial and error: Consider that initial tool choices may not always work out, but do offer learning and adaptability opportunities for the developers and the entire team.

Share successes across teams: Leverage internal channels to disseminate proven strategies, tactics, or tooling structures among different teams.

• Update your tool policies: Review and adjust company-wide tool policies to support this level of flexibility, and budget accordingly for the potential variety of tool choices.