Brian Balfour is a co-creator of Reforge, where he works on education and tools for product and growth teams. His posts discuss AI product development, including how teams can explore product ideas before building and help more people adopt prototyping tools.
Brian Balfour is known for building Reforge, which began with growth courses and expanded into a community and products for product teams.
His posts connect AI tools to the work teams still need to do: explore product options before building, avoid features customers do not use, and reduce the setup friction that keeps new people from adopting prototyping.
He also shares personal and community-focused posts, including asking his network to help a new food entrepreneur and recognizing people behind Reforge’s growth.
Balfour makes broad product-development concerns concrete.
He explains how faster execution can create product debt, then describes Reforge Build’s Variations feature as a way to compare four directions and their tradeoffs before making an interactive prototype.
In another post, he identifies the repeated setup work—design patterns, company context, and project details—that can block wider team adoption, and describes shared templates and context as a response.
This combination of strategic argument and specific workflow examples helps readers assess both what teams should change and where friction arises.
The available posts also show a less product-focused side: he uses his network to connect an entrepreneur with CPG expertise and publicly credits colleagues for Reforge’s work.
The evidence here does not establish a broader account of his earlier career or signature work beyond Reforge.
Brian Balfour's focus lies in navigating the profound shifts occurring in product development and growth strategy, particularly as artificial intelligence accelerates the creation of digital products.
Read more
He argues that rapid execution must be balanced by deep strategic validation and that organizational friction is the primary bottleneck to widespread AI adoption.
Preventing Product Debt in the Age of AI
Balfour argues that while AI tools allow teams to accelerate product execution dramatically—shipping features faster than ever—this speed inherently leads to 'mountains of product debt.' This debt consists of features that are built and shipped quickly but are ultimately unused by customers because the initial exploration and validation phase was insufficient.
Read more
The priority must remain on exploring multiple product options and understanding the full range of tradeoffs before committing to building. He stresses that simply building 'and hoping you picked the right direction' is no longer a viable strategy.
For AI to be effectively adopted across large teams, organizations must overcome significant 'activation energy' challenges.
Read more
A primary friction point is the need for every individual team member to rebuild core design patterns, gather company context, and set up project details from scratch for every new task.
To solve this, he promotes solutions like 'Teams' in Reforge Build, which provides shared design systems, common company context, and shared templates. This ensures that one person's foundational work can immediately serve as a starting point for an entire organization, dramatically speeding up prototyping cycles.
Balfour views the integration of AI not merely as a technical upgrade, but as a 'knowledge shift.' He posits that product teams require both new technological tools and a fundamental evolution of their expertise and knowledge base to successfully navigate the industry's most significant transition in decades.
Read more
As Reforge integrated with Miro, the goal was to ensure that the learning and expert-led courses provided by Reforge Learning could accompany new AI tools, focusing on the specialized knowledge required to operate effectively in the modern tech landscape.
Newcomers should start here to understand the operational and team-based challenges of scaling AI tooling and how design systems and shared context can overcome adoption resistance.
Read more
Balfour describes a common hurdle when introducing AI prototyping to teams: high friction where every user must rebuild design patterns, gather context, and set up project details. He introduces 'Teams' in Reforge Build to solve this by providing shared templates, design systems, and project context, accelerating team adoption and output.
For brands planning a campaign
This work provides concrete evidence of addressing enterprise friction in technology adoption. It is suitable for a talk demonstrating how B2B SaaS products can lower the barrier to entry for complex tools (like AI prototyping) by building centralized, shared resources.
Newcomers should read this to learn how to maintain strategic focus and mitigate the risk of launching unusable features despite technological advancements.
Read more
He argues that while AI is significantly accelerating product execution (shipping features faster), this speed risks creating 'mountains of product debt'—features that customers don't use. To combat this, he details the 'Variations' feature in Reforge Build, which encourages users to explore four distinct directions and tradeoffs before committing to a full prototype.
For brands planning a campaign
This offers a critical, strategic framework for product leaders struggling with the tension between speed and validation. It provides a powerful argument for why deep exploration (Product Discovery) must precede AI-driven execution.
Newcomers should read this to understand the macro-level implications of AI for professional skills and product team structure in the modern tech landscape.
Read more
Announcing Reforge's merger with Miro, Balfour frames the AI transition not merely as a technology shift, but as a 'knowledge shift.' He argues that product teams require both new tools and new knowledge to navigate this industry transition successfully, while Reforge Learning will continue to expand its specialized courses.
For brands planning a campaign
This work establishes a high-level strategic vision for the future of product management education. It positions the conversation beyond just tools, focusing on the necessity of specialized knowledge, which is valuable for organizations planning upskilling initiatives.
He argues that the rapid acceleration of product execution through AI tools significantly outpaces traditional product discovery.
Read more
Shipping faster is not enough; businesses must still explore multiple options and understand tradeoffs before building to avoid creating 'mountains of product debt.'
For brands planning a campaign
Brands can evaluate Brian Balfour's expertise to implement discovery processes that force strategic validation, ensuring AI-driven development results in highly useful, intended features rather than unutilized features.
He identifies major friction points in AI prototyping, such as the need for every team member to rebuild design patterns and gather company context.
Read more
He offers solutions, such as 'Teams' features, that provide shared templates, design systems, and project context, allowing one person's work to serve as a shared starting point for an entire organization.
For brands planning a campaign
This is relevant for B2B SaaS companies seeking to scale AI adoption across large teams, offering methods to drastically reduce activation energy and accelerate time-to-market while maintaining consistency.
Brian Balfour provides strategic insights into product and distribution shifts, viewing the business through lenses of organizational scaling, market disruption, and institutional growth (as seen in the evolution of Reforge).
Read more
For brands planning a campaign
For executive leadership, he offers strategic guidance on how to align product, engineering, and growth to navigate major industry transitions and ensure long-term viability.
Brian Balfour’s posts identify him as a co-creator of Reforge and describe Reforge’s products and its move to Miro.
Read more
The posts do not specify his ownership or employment status, or describe sponsorships or affiliate arrangements.
Reforge
Disclosed partnership
Balfour says he co-created Reforge’s first Growth Series with Andrew Chen and describes Reforge as a community and product business he helped build.
Read more
He later announced that Reforge was joining Miro, with Reforge Learning remaining a separate brand and other Reforge products being integrated into Miro. The posts do not specify Balfour’s ownership or employment status.
Balfour discusses launching Variations and Teams in Reforge Build, describing them as tools for exploring product directions and reducing friction when teams adopt prototyping.
Read more
The posts do not specify a separate commercial relationship between Balfour and the product.
Brian Balfour’s posts are useful if you want to understand why faster AI-assisted building does not automatically produce better products.
Read more
Start with the argument that execution has outrun discovery and that unused features create product debt.
Then look at the Reforge Build examples: Variations is presented as a way to explore four directions before committing, and Teams is about shared templates, design systems and company context so prototyping adoption spreads beyond one early adopter.
For the broader strategic frame, read the Reforge-Miro announcement and the distribution-shift update.
The work is aimed at product leaders and teams; it is more strategic than a tool tutorial.
Both write about AI changing product development and about reducing friction between design intent and what gets built.
Read more
Dils’s posts on AI-readable Figma files and talent-led teams overlap with Balfour’s concern that execution speed without shared context creates waste.
Dils gives hands-on design-system and file-organization guidance plus a talent-led org argument; Balfour frames the same pressure at the level of product strategy, discovery, product debt and Reforge’s platform and education work.
Both diagnose a gap between faster building and better decisions.
Read more
Walvekar’s posts on AI coding speed versus slow decision-making and on defining “done” connect directly to Balfour’s warning that AI execution can outrun discovery and create product debt.
Walvekar focuses on product-management decision-making and alignment around business outcomes; Balfour focuses on discovery, prototyping adoption and the organizational cost of unused features.
Both are interested in AI-era design tooling that gives people and agents better product context.
Read more
Antihi’s Designbase posts about a local-first design IDE and shared product ontology echo Balfour’s Reforge Build argument for shared templates, design systems and company context.
Antihi writes as a builder of design infrastructure, describing a specific IDE and product ontology; Balfour writes as a product and growth educator and operator, connecting tooling to discovery, product debt and team adoption.
Brian Balfour is heavily involved with Reforge, a leadership platform focused on product and growth education, which has been acquired by Miro.
Read more
His public activity centers on product innovation, especially around leveraging AI for product execution and mitigating product debt. While the provided evidence does not detail formal third-party partnership or sponsorship opportunities, it demonstrates engagement through high-level thought leadership, platform development (e.g., Reforge Build), and keynote speaking engagements.
Thought Leadership & Content
Buyer requirement
Acquiring brands seeking expert insights on AI, product management, and B2B SaaS growth strategies, often via courses or high-level content creation.
Keynote Speaking & Events
Buyer requirement
Speaking engagements at industry conferences (such as Canvas 26) discussing trends like distribution shifts and product execution evolution.
Product/Platform Integration
Buyer requirement
Collaborations or integrations related to expanding the functionality of the Reforge platform or its research tools (Reforge Insights, Build) within a broader ecosystem, such as Miro.
A large-scale B2B SaaS platform aiming to embed Generative AI into its core product offering needs to address adoption friction and ensure that speed does not lead to wasted development effort.
Read more
Brian Balfour is a strong fit because his work specifically tackles the risks associated with AI execution acceleration, such as the creation of 'product debt'—features that are shipped but unused. His expertise is centered on providing the strategic guardrails (Product Discovery) required before high-velocity AI implementation.
When to choose a specialist
A consumer-facing local business, such as a small brick-and-mortar retail chain, that is seeking basic operational advice or general marketing tips.
Read more
While Brian Balfour is interested in supporting new entrepreneurs, his primary focus is on complex technological shifts, high-growth product strategy, and enterprise-level tools (Reforge Build, Miro integration). His insights are too specialized and abstract for general, non-tech operational challenges.
A worked campaign example
Campaign Angle: Strategic Executive Keynote (Target: CTO/Product VPs at a major Enterprise SaaS Provider).
Talk Title: 'From Feature Velocity to Value Velocity: Balancing AI Execution Speed with Product Discovery Integrity.' Presentation Focus: The presentation would detail how current AI tools allow for unprecedented shipping speed, but argue that without disciplined discovery (like exploring 'Variations' or using standardized design systems,, organizations risk overwhelming customers with unusable features.
He would propose a 'Knowledge Shift' framework for leadership, helping them navigate the transition by pairing rapid AI deployment with rigorous validation protocols, ensuring engineering effort translates into real customer value.
Choose Dils when the adoption problem starts in the design file.
Read more
Dils's posts give a concrete checklist for making Figma files legible to AI tools: group components by domain, build sticker sheets with instances, remove documentation and hidden layers from component pages, use semantic layer names, apply Auto Layout, and add code syntax to variables.
Dils also argues for talent-led teams built around capabilities rather than fixed roles.
For this brief, that makes a stronger talk for a design-operations audience that needs to clean up the inputs AI prototyping tools depend on.
The evidence is concentrated on design-file hygiene and team structure.
Dils's posts do not address product discovery validation, product-debt measurement, or how to run a discovery process before building.
A talk would be more of a design-ops workshop than an executive session on balancing AI execution with discovery.
Choose Walvekar when the bottleneck is the decision after prototyping, not the prototyping itself.
Read more
Walvekar's posts argue that AI coding tools speed up building while decisions still take weeks, and that the harder question is whether a feature should be built.
A second post asks teams to define 'done' in business-outcome terms before work starts.
For this brief, Walvekar is the better pick when the client needs alignment on success criteria and decision rights so faster prototyping does not create unused features.
Walvekar's evidence is about decision-making and definition of done, not AI prototyping adoption mechanics.
The posts do not cover design systems, prototyping tools, or a discovery workflow.
A talk would be a decision-hygiene session rather than a practical guide to getting teams to adopt AI prototyping.
Choose Antihi when the client wants to put product context directly into the tools people and agents use.
Read more
Antihi's posts describe Designbase, a local-first design IDE that sits on the real codebase and brings components, code, patterns, rules, tools, and decisions into a shared product ontology.
That is relevant when the adoption problem is that agents lack context about the product and designers work in mockups that drift from code.
Antihi's framing—design in the running product and give agents the same context—fits a client that wants tooling close to the codebase.
Antihi's posts are launch and testing-access announcements.
They do not report adoption results, product-debt reduction, or independent customer outcomes.
A talk would lean toward a product walkthrough and a bet on where design tooling is going, not a neutral discovery framework or a proven adoption program.
The analysis focused on Balfour's strategic arguments regarding the challenges of AI product prototyping, the operational design of Reforge platform features like 'Variations' and 'Teams,' his insights into growth and product evolution, and his reflections on the history and milestones of Reforge and its integration into Miro.
Recent engagement
Across their last 5 LinkedIn posts, the median post got 200 reactions and 95 comments. Checked 2026-11-02.
