Andrew
Dec 24, 2025 - Apr 7, 2026
7
Decisions
0
Active Todos
4
Patterns
Categories
Decisions (7)
Committed to Improve Team Bandwidth Visibility in Monday Meeting
Committed to discuss with Nathan how to improve visibility in the Monday meeting on team bandwidth and impact, after Andrew raised he lacks visibility into other teams' work and hesitates to ask for help for fear of disrupting higher-priority work.
CentOS Bridge Deprioritization Held Despite Customer Risk
Confirmed to Andrew Jorgens that CentOS Bridge is consciously deprioritized. Acknowledged customer reputation risk (customer re-evaluating contract after only 4 CVE fixes) but held the line, explaining that 'important' is insufficient justification - a project must be more important than something else currently being worked on.
Sensitive Decision
Leadership 1:1s with Maple, Dieter, Andrew
Decision to begin regular 1-on-1s with Maple, Dieter, and Andrew (when onboarded) to build trust and ensure unified messaging.
Andrew Jorgensen Level Flexibility Confirmed
Clarified with Brianne that Andrew does not need to come in as Maxs peer. Happy to slot him into either the more senior or less senior position based on his comfort. Want him coming in feeling happy and excited about what hes signing up for.
Andrew Jorgensen Hiring Approved
Approved hiring Andrew Jorgensen for an IC role reporting to Nathan Blackham. Offered flexibility on level - he can come in at senior or less senior position based on his comfort.
Andrew Jorgensen Hiring - Deferred to Role Clarity
After CTO interview for Sr. Linux System Engineer, did not fill in final hire/dont recommendation. Deferred to Max/Nathan to clarify what they want him doing and culture fit concerns.
Related Patterns (4)
Proactive Talent Pipeline Investment
Invest in building leadership bench and talent relationships before there is an urgent need. Use proven relationships from past experience to create optionality.
Lead by Example with New Tools
When championing new tools or processes, personally use them and share results rather than just advocating. Learning by doing and demonstrating value through example is more effective than mandates.
Accountability Follow-Through
When you issue a warning or mandate with stated consequences, you follow through. Warnings are not threats - they are commitments. The credibility of future accountability depends on following through now.
Protect Engineering Focus Through Process
When faced with requests that would disrupt engineering focus (from sales, governance, product, or other stakeholders), establish processes that protect engineering ability to innovate while still satisfying legitimate concerns. Prefer systematic solutions over ad-hoc responses.