Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

James McAulay recommends growth people get at least read-only access to the company Git repo, even if they cannot ship code. With event definitions visible, they can answer their own questions about when events fire, which version is current, and why duplicates exist instead of pinging engineers on Slack.

Related Insights

Allowing PMs to commit code is not a cultural choice but a reflection of system maturity. It's safe only with robust CI/CD and automated testing. In immature systems, it creates shadow work for engineers and introduces risk.

To build trust and prevent errors, treat AI agents like new employees by starting them with limited, read-only access to your systems (e.g., calendar, email). Only after they have demonstrated understanding of your workflows and priorities should you grant them write access.

An engineering firm initially siloed access to departmental folders. They found that when an engineer's input was needed on a sales quote or marketing material, the project would stall while waiting for IT to grant access. Giving broad access by default removes this friction and speeds up cross-functional work.

Manage collective team context—docs, queries, research—in a version-controlled repository. Everyone, including non-technical members like ops and strategy, contributes via pull requests, creating a single, evolving source of truth for AI agents and humans.

To overcome engineering hesitancy about giving customer-facing teams codebase access, highlight the benefit to engineers themselves. Position it as a solution that eliminates their need to answer constant, last-minute pings and DMs, freeing them from being an information bottleneck.

By organizing all product documents—PRDs, quarterly plans, research, and meeting notes—into a version-controlled GitHub repository, PMs create a single source of truth. This "product repo" becomes a structured environment that AI agents can easily navigate to access context and generate new artifacts.

Move beyond fragmented tools like Notion for PMs and Figma for designers. By using a single, shared GitHub repository for business context, product briefs, designs, and code, teams can create joint context and dramatically increase alignment and speed.

With AI, codebases become queryable knowledge bases for everyone, not just engineers. Granting broad, read-only access to systems like GitHub from day one allows new hires in any role (product, design, data) to use AI to get context and onboard dramatically faster.

AI tools connected to GitHub allow non-technical roles to conduct "forensic investigations" of a codebase. By prompting an AI, they can generate a full timeline of commits and PRs for a specific feature, providing ground-truth context during business incidents without needing engineering help.

To encourage designers intimidated by Git and terminals to use a code playground, Notion created custom slash commands like `/create` and `/deploy`. These commands abstract complex processes, provide instructions if prerequisites are missing, and guide users through workflows like branching and deploying, lowering the barrier to entry.