Tag: leadership

  • WordCamp Canada 2025 conference talk

    WordCamp Canada 2025 conference talk

    I’m thrilled to share how the Shipping WordPress Without Shipping Code talk went at WordCamp Canada 2025 (aka “WCEH”; get it WC, eh?).  For folks who couldn’t attend, here’s a summary of what we covered, insights from the audience, and next steps you can try yourself.

    If you’d rather watch than read, here’s the full WordCamp Canada 2025 talk:

    In the talk I walked my own path, from helper to release deputy to AI team lead, all without ever having commit access.  Along the way I shared how non-developer roles often get overlooked, practical patterns I’ve used to keep releases moving, and encouragement for designers, strategists, writers, or project leads who want to jump into this space.  Here’s how the session unfolded, with some highlights and sample quotes.

    A close up of a sign

    Opening & Framing

    I started by confronting the myth that only engineers lead in open source.  My aim was to shift perspectives: YOU can lead, even if your strengths lie outside code.

    The Historical Gap

    We talked about how WordPress projects have historically lacked project and product management support, and how that gap creates friction.  I quoted from the WordPress release handbook:

    “The main focus of the release team is to lead the release from its beginning through to launch … to act as connectors and facilitators.”

    It resonated: many in the audience nodded when I called out that non-developer contributions are often invisible or undervalued.

    My Journey

    I shared my own timeline: involvement in WordPress 4.7, then 4.8, 4.9, 5.8, 6.1, and 6.8.  I also noted that WordPress 4.7 had 482 contributors, including 205 first-timers, to emphasize how major release cycles need more scaffolding than code alone in order to support that many new contributors.

    What “Glue Work” Looks Like

    This was a core section of my talk.  We broke down how “glue work” such as triage, alignment, decision logging, and volunteer motivation is the connective tissue in a release.  I used the quote:

    “Triage is the practice of reviewing existing issues to be sure they are relevant and actionable.”

    And I referenced how Apache PMC members and Kubernetes maintain non-coding roles, showing that this isn’t just WordPress-specific but a pattern in mature open source communities.

    Tools, Patterns, & Gotchas

    Here, the audience got actionable advice. Some highlights:

    • Use GitHub issues and projects with clear labels (needs-decision, punt, etc.)
    • Maintain decision logs so the same debates don’t repeat
    • Establish scope gates (feature freeze, RC readiness) to protect the release timeline (go/no go decisions)
    • Beware burnout and invisible labor

    I referenced Karl Fogel’s Producing Open Source Software from my notes in a recent WordPress Book Club hosted by Aaron Jorbin roughly as ~“If it’s not written down, it didn’t happen.” And Nadia Eghbal’s note that “Maintainers simply don’t have the energy to onboard every person who shows passing interest.”

    From Contributor to Leader

    We laid out a three-step path:

    1. Start small: take notes, triage, run a meeting agenda.
    2. Own a lane: coordinate docs, dev notes, or release notes.
    3. Lead a release: coordinate across teams, make decisions, facilitate.

    I also referenced the Kubernetes “leads and shadows” model as something WordPress could use to mentor future contributors.

    Practical Playbook

    Seven habits you can take into your own contributor journey:

    1. Write the agenda, end on time
    2. Keep a decision log
    3. Guard scope with labels
    4. Close stale issues
    5. Default to public and async
    6. Give credit often
    7. Leave breadcrumbs

    I urged the audience to pick one habit and try it immediately.

    Takeaways and Q&A

    I wrapped up by reinforcing that leadership lives outside the repo and glue work makes shipping possible.  I invited folks to pick a lane, join a triage session, or help curate the next release.

    The question period surfaced great stories: people surprised they could participate in release work without code, and others asking how to balance contributions with full-time jobs.

    What I Learned from the Room

    • Many talented people hesitate because they don’t see non-developers in core.
    • The “playbook” habits resonated; people wrote them down quickly.
    • There’s appetite for more structured mentorship paths for project contributors.
    • Some folks suggested pairing systems (non-developer lead and developer lead) to onboard new contributors.

    Next Moves You Can Try

    • Join the next WordPress core triage or bug scrub session.
    • Volunteer to take notes for a devchat.
    • Pick one of the seven playbook habits and try it in your own project or team.
    • Consider how your current job or project might adopt glue roles, like coordinating features, managing scope, or writing decisions.

    Final Thoughts & Thanks

    Before wrapping up, I have to say how special it was to experience WordCamp Canada in Ottawa.  The Carleton University campus was absolutely stunning, with crisp fall air, the leaves just starting to turn, and Richcraft Hall overlooking the canal and nearby lake creating an incredible setting.

    A red and white flag with a white w in the middle

    Ottawa itself is a beautiful mix of history and energy, with old architecture and monuments along the Ottawa River that show how much care the city puts into preserving its character.

    And of course, none of this would have been possible without the amazing organizers, volunteers, and sponsors who made WordCamp Canada feel every bit like the flagship event it is becoming.  The warmth and generosity of the Canadian WordPress community really stood out, from hallway conversations to contributor day collaborations.

    Running this talk in Canada felt meaningful.  It’s part of a larger conversation: WordPress needs more voices who see beyond code, people who connect, facilitate, and help the system work.  I can’t wait to see what happens when more contributors realize they are leaders already.

    If you were in the session, thank you.  If we met, thanks again.  If not, I hope you’ll drop me a line, try one small piece of this playbook, and remember that leadership doesn’t always look like a commit; sometimes it’s the work no one sees, but everyone depends on.

    If you missed the talk, then below are my slides.

    Fediverse Reactions
  • Why I Wrote a Personal README (and Why You Should Too)

    Why I Wrote a Personal README (and Why You Should Too)

    I value transparency, collaboration, and clarity whether that’s working with colleagues, contributors in the WordPress community, or clients.  But one thing has become clear over time: everyone works differently, and understanding those differences upfront makes for smoother, more effective collaboration.  Enter the Personal README.

    Inspired by Luc Levesque, Roy Rapoport, and 18F’s guide on Personal READMEs, I put together my own as a way to share how I work, communicate, and approach leadership.  It’s a snapshot of my work style, values, and expectations, both for myself and for those working with me.

    ???? Check it out here: jeffpaul.com/readme/

    Why Write a Personal README?

    A Personal README isn’t a set of hard rules, it’s a tool to set expectations, remove ambiguity, and help others understand how to best work with you.  It can cover things like:

    • Your working hours and communication preferences
    • Your approach to meetings and collaboration
    • What makes you excited (and what chafes you or makes you grumpy)
    • How you give and receive feedback

    By being upfront about these things, you can reduce friction and make it easier for colleagues to engage effectively.  It also helps new team members ramp up faster, since they don’t have to guess what works best.

    My Challenge to You

    If you haven’t written a Personal README yet, I highly encourage you to give it a shot!  Start with something simple and iterate over time.  Ask yourself:

    • What’s important to me in how I collaborate?
    • What do I expect from my teammates?
    • How do I like to communicate and make decisions?

    And if you do create one, share it!  Put it in your profile on social networks and communication platforms as well as your personal website (you own your own content right?!), basically wherever people can easily find it.  The more we normalize transparent communication, the easier it becomes to work effectively together.

    If you already have a Personal README, I’d love to see it!  Drop a link in the comments or tag me on Bluesky / Mastodon / LinkedIn or wherever we connect.

    Let’s make working together easier. ????

  • Reblog: The 6 Mistakes You’re Going to Make as a New Manager

    Reblog: The 6 Mistakes You’re Going to Make as a New Manager

    Reblog via Matheus Lima‘s Terrible Software:

    Moving from an Individual Contributor (IC) to a manager is a significant career step. This is especially true in the ever-evolving tech industry. This change brings new challenges and opportunities to learn.

    Reflecting on my first couple of years as an Engineering Manager, I realized that the lessons I learned are not unique to me; many new managers face similar experiences. That’s why I want to share these insights with you. My goal is to support and connect with other new managers who are going through this exciting yet demanding transition.

    ???? Delegation

    The most common trap you’ll probably fall into is the (many times, subconscious) reluctance to delegate. Transitioning from an IC to a manager, I found myself attached to old responsibilities, unable to trust my team with tasks I used to do.

    You’ll rationalize it, “they won’t be able to do it the same way I’d do it,” but even if this is true (it’s not), long-term thinking you want your team to be able to tackle the things you used to do. Otherwise, they won’t grow — and neither will you.

    Remember that delegation isn’t about randomly distributing tasks; it’s about empowering your team, trusting them, and stepping into your new role as a leader.

    ???? Where’s my dopamine?

    For over a decade, my dopamine (from work) came from a very predictable place: shipping new things. As a manager, those direct rewards will simply disappear, leaving you feeling unfulfilled for weeks (months in my case).

    I won’t lie; this isn’t a solved problem for me yet, but I think I got into a much better shape by (trying to) rewire my brain into getting satisfaction from other places: giving feedback, seeing my reports grow, writing a very thorough performance review, etc.

    Keep in mind that we’re not the stars anymore; we’re facilitators. Yes, it’s true that we don’t ship a project directly anymore, but we’re helping our team ship all projects.

    ???? Quality over quantity

    It’s easy for new managers to equate the growth of their team size with personal and professional success. In my early days, I found myself desiring more team members or even additional teams, believing it’d reflect my management skills — and, of course, lead to a salary raise.

    However, I soon learned that this was a mistake. True growth comes from the quality of your team’s output, not from the quantity of its members. Focus on pushing your team to the next level; create a place where they can come up with new ideas and do great work. This not only leads to higher quality work but also to a more cohesive and happier team. Remember, a smaller team that works well together can do better than a bigger team that doesn’t.

    ⚖️ The level of engagement

    The right amount of engagement that you should have in your team’s projects is also a tricky subject. Lean in too much, and you’re micromanaging; lean out too much, and you appear disengaged.

    To find the right balance, consider the concept of Guided Autonomy. This means setting clear goals and expectations, then stepping back and letting your team figure out how to achieve them. Your role becomes less about directing every action and more about providing guidance. This approach promotes responsibility and growth within your team while ensuring alignment with project objectives.

    In my journey, I’ve learned that effective engagement means being present without being overbearing. It’s about creating an environment where your team feels supported but also free to innovate and take ownership. The key is to offer guidance and support without taking away your team’s independence.

    ????️ Managing perception

    As an individual contributor (IC), your work spoke for itself; people could easily see it. Plain and simple. As a manager, it’s less black and white, and surprisingly, for many new managers, part of your job now involves managing how others see you.

    With your team members, it’s about making sure they understand and appreciate your role as a facilitator of their success. You’re no longer directly creating the product, but you play a crucial role in guiding the process, overcoming obstacles, and creating an environment where creativity and productivity thrive. It’s important for your team to recognize and value this shift in your contribution — from individual accomplishments to team successes.

    Externally, the challenge is different but equally important. Stakeholders, other departments, and senior management may not see the day-to-day impact you have on your team. Here, managing perception involves actively communicating your team’s achievements and how your leadership contributes to these successes. It’s not about taking credit for the work, but about highlighting your role in empowering your team to excel. It’s a delicate balance of showcasing the team’s work while making your leadership and its positive effects visible to those outside of your immediate group.

    I understand how controversial this can be, and it’s one of the reasons why ICs often hesitate to transition into management (“all that politics!”). But it is what it is, so it’s important to adapt. Perception management is about clarity and visibility, not just for your own benefit but also to accurately represent your team’s efforts.

    ???? Redefining success

    It’s quite common for ICs to have impostor syndrome, but for managers — especially new ones — this will reach a whole new level.

    You’ll often question your work or even if there’s any value in anything that you’re doing. I’ve been there, and from what I learned, success for you is as simple as asking yourself two questions:

    1. Is my team shipping?
    2. Are they happy?

    If the answer is “yes” to both, don’t worry; you’re crushing it. ????


    Every new manager makes mistakes, but each one is an opportunity to grow. Embrace these challenges as part of the learning process. Becoming a skilled manager takes time and continuous learning. Keep pushing forward, and soon, your mistakes will become milestones in your management career.

    I’d love to hear about your journey as a new manager. What challenges have you faced, and what lessons have you learned? Share your stories and insights below or contact me directly.

    So, for those just scanning, that breaks down to:

    1. Delegate Effectively: Assign tasks to team members, trust their capabilities, and focus on mentoring rather than doing everything yourself.
    2. Celebrate Team Success: Shift your sense of accomplishment to your team’s achievements and take pride in their growth and progress.
    3. Prioritize Quality: Aim to enhance the team’s output and collaboration rather than focusing on expanding the team size.
    4. Balance Involvement: Set clear goals and provide guidance while allowing the team autonomy in their execution.
    5. Communicate Contributions: Regularly share the team’s successes and your role in supporting them to ensure your impact is visible.
    6. Stay Adaptable: Approach new challenges with curiosity and a willingness to learn as you grow into your leadership role.

    This is such a perfectly wonderful TLDR for those moving into being a first time manager, but also a reminder for those who’ve been a manager perhaps even with multiple layers of an organization under you on six great actions to help position you as a leader that people will almost certainly WANT to work with!

  • Being a better ally and reflecting on yesterday’s actions

    Being a better ally and reflecting on yesterday’s actions

    TLDR; Yesterday I was insensitive towards Anne McCarthy and for that I deeply apologize and recognize the need to improve.

    As a person who belongs to a demographic that historically holds privilege, I’ve made it a personal commitment to advocate for empathy and support towards those whose experiences differ from mine.  In both my personal and professional lives, particularly within the open web community, I strive to exemplify allyship by fostering an inclusive and supportive environment.  It’s crucial that people like me call out behaviors that don’t align with these values, aiming to ensure that everyone feels welcome and valued in our community so that it can be a place where the principle of “welcoming contributions from anyone” is more than just a slogan but a lived reality that I want all to experience.

    Yesterday I failed to meet these expectations and, in doing so, created a negative experience for Anne McCarthy, who was facilitating the weekly devchat meeting for WordPress core.

    In the heat of the moment, I overlooked crucial contextual cues from Anne and others in devchat, reacting impulsively to a topic that struck a nerve with me. The specifics of what triggered my reaction are inconsequential compared to the impact my actions had on Anne.  Having served as a WordPress core Team Rep for over three years, I understand firsthand the challenges of managing an online forum and maintaining the collective focus during hour-long discussions.  I’ve witnessed how certain individuals can dominate conversations, stifling diverse viewpoints and limiting the exploration of other topics.  Yesterday I regrettably embodied the very behavior I wish to mitigate.  I must do better.

    I deeply admire and respect Anne’s incredible work with the Full Site Editing Outreach Program and their tireless efforts to enhance communication within the WordPress project and foster connections with the community. Anne’s dedication to inclusivity and collaboration serves as an inspiration to me and many others.  The impact of Anne’s work on the project and the broader open web community is immeasurable. I aim to be someone who not only supports such invaluable efforts but also works to amplify them.

    Anne deserves a sincere apology, and our community deserves leaders who are empathetic, supportive, and inclusive.  While I aspire to be one of those leaders, it’s evident that I have room for growth.

    Anne, I am genuinely sorry.