# My Personal README

- Link: https://jeffpaul.com/readme/
- Published: 2025-03-06T13:27:15-06:00
- Author: jeffpaul

## **Introduction**

I created this Personal README to help others understand how I work, communicate,
and collaborate both internally with colleagues and externally in open-source communities
like [WordPress.org](https://wordpress.org/).  My goal is to make interactions smoother,
set clear expectations, and provide transparency into my work style and values. 
If we’re working together, I hope this helps us align and collaborate effectively.

This README is inspired by the work of [Luc Levesque](https://coda.io/@luc-levesque/blueprint-for-leaders-managers-communicate-your-quirks/my-blueprint-9)(
who first shared the concept in 2012), [Roy Rapoport](https://bit.ly/roy-latest-readme)(
whose Manager README at Netflix popularized the idea), and the [18F guide on Personal READMEs](https://blog.18f.org/2020/03/05/readmes-for-you-and-me/).

---

## **My Working Style**

### **What I value**

 * **Open Source First** – The long-term success of WordPress as an open-source 
   project comes before individual or company interests. I advocate for sustainable
   decision-making that prioritizes the health of the ecosystem.
 * **Transparency & Collaboration** – I believe in working in the open, sharing 
   information freely, and ensuring decisions are made with broad input.
 * **Autonomy with Accountability** – I trust my team and contributors to take ownership
   of their work while expecting follow-through on commitments.
 * **Constructive Debate** – Thoughtful, well-reasoned discussions make open-source
   stronger.  I welcome disagreement when it’s productive and solution-oriented.
 * **Pragmatism Over Perfection** – While I value high-quality work, I also believe
   in shipping and iterating.  The best solution balances idealism with real-world
   constraints.  Those who regularly work with me are familiar with my “ok now tell
   me what I’m an idiot and a different approach is better” comment.

---

## **How I Work**

### **My preferred communication style**

 * **Asynchronous first** – I prefer discussions via blog posts (e.g. personal blogs,
   community ones like [make.wordpress.org](https://make.wordpress.org/), or as 
   necessary private company-based ones), Slack, or GitHub to keep things moving
   efficiently.
 * **Structured and concise** – When reaching out, I appreciate clear context and
   a specific request or question.  I aim to provide the same in return.
 * **Decision-oriented** – Discussions should lead to action.  If we’re stuck in
   a loop, I’ll help push toward a next step.
 * **Real-time when necessary** – Some conversations are better had synchronously,
   especially when working through complex issues or blockers.  I’m happy to jump
   on a call when needed.

### **What I expect from others**

 * **Take ownership** – If you see an issue, raise it.  If something needs doing,
   step up.  I value proactive problem-solving and will usually reward that with
   trust and authority, but beware with that comes responsibility.
 * **Provide context** – Help me (and others) understand the ‘why’ behind what you’re
   asking as it makes collaboration smoother.
 * **Respectful disagreement** – Challenge ideas, not people.  I welcome pushback
   when it makes us all better.
 * **Document decisions** – Open-source moves fast, and institutional knowledge 
   can get lost.  Capture decisions in a public, persistent place whenever possible.

### **What you can expect from me**

 * **Support and unblocking** – My role is not to micromanage but to help clear 
   roadblocks, whether they’re technical, process-related, or organizational.
 * **Direct and fair feedback** – I give constructive feedback with the goal of 
   improving outcomes.  I also welcome feedback in return.
 * **Strategic thinking** – I look beyond immediate problems to ensure we’re making
   sustainable decisions for the long term.
 * **Follow-through** – If I commit to something, I’ll get it done or communicate
   if I cannot.  I expect the same from others.

---

## **Giving Feedback on This Document**

I consider this README a living document, and I welcome feedback to make it more
useful and reflective of how I actually work. Your input helps ensure that this 
remains accurate and valuable for those working with me. If you have suggestions,
corrections, or additional thoughts, feel free to reach out to me via:

 * **Email** (if you have it)
 * **Slack DM** (if we’re in the same workspace)
 * **Commenting on this page itself**

### Share this:

 * [  Bluesky ](https://jeffpaul.com/readme/?share=bluesky)
 * [  Mastodon ](https://jeffpaul.com/readme/?share=mastodon)
 * [  LinkedIn ](https://jeffpaul.com/readme/?share=linkedin)
 * [  Print ](https://jeffpaul.com/readme/#print?share=print)
 * [  Email ](https://jeffpaul.com/readme/?subject=%5BShared%20Post%5D%20My%20Personal%20README&body=https%3A%2F%2Fjeffpaul.com%2Freadme%2F&share=email)
 * [More](https://jeffpaul.com/readme/#)

 * [  Facebook ](https://jeffpaul.com/readme/?share=facebook)
 * [  Nextdoor ](https://jeffpaul.com/readme/?share=nextdoor)
 * [  Pinterest ](https://jeffpaul.com/readme/?share=pinterest)
 * [  Reddit ](https://jeffpaul.com/readme/?share=reddit)
 * [  Telegram ](https://jeffpaul.com/readme/?share=telegram)
 * [  Tumblr ](https://jeffpaul.com/readme/?share=tumblr)
 * [  WhatsApp ](https://jeffpaul.com/readme/?share=jetpack-whatsapp)

### Like this:

Like Loading…

## Comments

### By: James Rovira

- Link: https://jeffpaul.com/readme/#comment-2806
- Published: 2025-04-03T13:06:41-05:00

Great ReadMe. The link to the 18F guide is now broken as are many .gov links.

Loading...

### By: jeffpaul

- Link: https://jeffpaul.com/readme/#comment-2825
- Published: 2025-04-25T14:27:08-05:00

Looks like a find/replace from “18f.gsa.gov” to “blog.18f.org” fixes that now.

Loading...
