Devin Walker joins the Jukebox Podcast to discuss his new role as Artistic Director (head) of Jetpack at Automattic. Devin is best known as co‑founder of GiveWP and creator of WP Rollback, with extensive experience in development, design, marketing, and support. After GiveWP was acquired and time at Liquid Web, he left in August 2025 and accepted the challenge of leading Jetpack—drawn by the product’s reach and the opportunity to have broad impact within Automattic and the WordPress ecosystem.
Why Jetpack?
Devin weighed starting another independent venture against joining Automattic. Jetpack’s scale, influence, and complexity appealed to him: it touches millions of sites and integrates tightly with wordpress.com. He acknowledged Jetpack’s divisiveness and the “jack of all trades, master of none” critique, but saw room to bring focus, polish, and clearer product direction.
Scope and priorities
Jetpack bundles many capabilities—stats, backups, security, performance, social sharing, forms, VideoPress, basic SEO, and more. Devin’s immediate aim is not to keep adding disparate features but to refine and improve what exists, prioritizing the most impactful areas. Forms is a major focus: recent releases (15.2 and upcoming 15.3) include significant upgrades, and Devin leads that initiative to make forms much more useful to the majority of users while acknowledging that highly specialized power users will still need dedicated tools.
Organization and development approach
Automattic’s structure is evolving from a traditional functional org to a more matrixed model. Rather than isolated Jetpack teams, there’s now shared architecture and design resources that span .com, Jetpack, WooCommerce, and other products. This creates opportunities for tighter integration—Jetpack supplying the cloud services and “secret sauce” to enhance self‑hosted sites—while also requiring coordination across teams.
Devin describes the environment as more liquid and collaborative: engineers and designers can be focused on specific initiatives like forms, then shift to other priorities as needed. That flexibility enables better cross-product work (e.g., Jetpack + WooCommerce) but requires careful resource choices and roadmapping.
AI and the future of site building
AI is a major area of investment. Jetpack already has understated AI features—automatically generating excerpts, featured images, and other content aids—and Automattic is building a much larger AI effort to bring .com capabilities to self‑hosted WordPress via Jetpack. A sizable engineering team is working on a rewritten foundation for AI features that will act as a “content companion,” offering assistance throughout the WP admin and offering tools for visitor engagement, conversions, presales, and more.
Devin highlights Telex (Automattic’s block‑generation tool) as an example of what’s possible: AI could let users generate custom blocks or functionality on the fly (e.g., a seasonal visual effect, a bespoke block for a specific content need) and Jetpack can become the bridge that manages, deploys, and updates those generated pieces across sites.
Focus, simplification, and UX
A recurring theme is the need to simplify Jetpack’s UX and marketing. Users face confusing overlaps—multiple toggles, scattered controls, unclear dependencies with wordpress.com, and inconsistent behavior across classic and block themes. Devin wants to consolidate toggles, streamline onboarding, and apply frameworks like Jobs to Be Done to understand user goals rather than assuming feature‑driven flows.
Because Jetpack has a core install base around four million sites, changes must be careful and measured. Automattic follows a monthly release cadence, and reliability is critical: major causes of low reviews are breaking changes and poor support. Devin plans to balance careful rollouts with more aggressive improvement where safe, using onboarding and improved navigation to better explain Jetpack’s value.
Marketing and communication
Devin sees a gap in marketing resources relative to Jetpack’s potential. Historically Jetpack benefited from being an early, broad product, but the plugin ecosystem has matured and competitors now have focused marketing. He intends to boost Jetpack’s public communication—publishing more of the internal work that’s currently on P2s, refreshing messaging, and clarifying what Jetpack does and for whom. Improving public perception will be a key part of the plan alongside product changes.
Community, feedback, and next steps
Devin emphasizes using user feedback to guide changes and avoid working in a bubble. He’s been meeting across teams, documenting product histories and responsibilities, and publishing a P2 called “Connecting the Dots.” He invites users to try Jetpack as it is now, provide feedback, and follow the planned improvements.
Contact and accountability
For feedback, Devin points to [email protected], jetpack.com/feedback, or reaching him on Twitter (@innerwebs) and his site (devin.org). Nathan and Devin agreed to a public check‑in in 12 months to revisit progress and measure improvements in UX, reviews, and cohesion.
In short: Devin took on Jetpack to bring focus, polish, clearer UX, and deeper AI integration to a sprawling but powerful product. He plans to consolidate and improve core capabilities (forms, onboarding, SEO basics), integrate AI to act as a content and site-building companion, strengthen marketing and communication, and do so carefully given Jetpack’s large user base.
