Lindsay
Jan 2, 2026 - May 12, 2026
15
Decisions
1
Active Todos
6
Patterns
Categories
Decisions (15)
Commit engineering to vuln-handling infra/automation at Leadership Roundtable
At the 5/11 Leadership Roundtable, Peter accepted an explicit action item to prioritize vulnerability-response infrastructure and automation work in engineering, and to update Chris Baek as the interim process owner. The commitment converts the 5/8 internal-to-engineering commitment (build/test infra to eliminate reactive interrupts) into a cross-functional commitment with Bjorn, Greg, Chris, and Lindsay in the room.
Documentation process — Product defines exit criteria in Jira, Engineering delivers
Formalize documentation ownership: Product defines documentation requirements in Jira ticket exit criteria (e.g., docs suitable for blog post). Engineering delivers content meeting those criteria. Product or Marketing (Lindsay) refines technical content into user-friendly format.
Ship CIQ kernel patch with extra fix; contribute upstream; race to be first/best on CVE response
Linux kernel CVE response: CIQ shipping 10 fixes vs CentOS Stream's 9 (CIQ found and is fixing an extra issue related to the CVE). Extra commit submitted upstream to centos-stream and acknowledged for inclusion. CIQ pushing to be first EL distro to release, with primary goal of customer reassurance and secondary goal of public proof point that CIQ contributes to security and is large enough to serve big customers. Also pushing patches to RLC kernels as fallback in case RH doesn't move quickly.
RESF JIRA Date Reset for Realistic Expectations
Peter directed Nathan and Justin to adjust April/May JIRA items with low confidence due to RESF resource drain. Move them out now to give marketing a high-confidence scope for 4-6 weeks.
RESF Communication & Information Control Strategy
Established multi-layered communication control for RESF transition: (1) Posted own #engineering message with different language than Greg's draft, emphasizing visibility requirement. (2) Told eng-management nobody talks on RESF Zoom calls because RESF members can hear. (3) Asked Lindsay to confirm no social media leaks. (4) Told Max to keep RESF off Department Heads agenda Thursday.
Post-RESF Consolidated Deliverable Reset
Decided to deliver a single consolidated update to Lindsay on revised March deliverables after RESF work stabilizes, rather than incremental delay announcements. Nathan will reset all project dates at once.
Demanded war-room or date ranges for RLC Pro release dates
Marketing (Lindsay Aamodt) published release dates in #department-heads: Feb 19 RLC Pro, Feb 26 RLC Pro AI, Mar 5 RLC AMD. Justin Haynes responded that dates were 'written in light pencil.' Peter directed Justin: if dates aren't confident, either commit with a war-room to hit them, or provide GTM with ranges now so they can plan. Justin acknowledged and scheduled time with leads.
RESF crisis comms - single source of truth
In a RESF crisis, publish one official blog post as the central source of truth. All responses on social media (Hacker News, LWN, HPC forums) link back to that post. Do not engage in real-time debates. Own the traditional news cycle, not social media.
Engineering dates commitment by Friday - reprioritize for revenue impact
Committed to publishing updated engineering dates/milestones by Friday for Monday group review. Acknowledged January deliverables are unrealistic - many items were newly added and cannot complete in remaining ~10 days. Will reprioritize toward revenue-impacting items first. Tomorrow all-day session with Chris Baek to rework H1 plan into aggressive but achievable targets.
All-Hands messaging: acknowledge Q4 miss, pivot to pipeline optimism
Aligned with leadership on All-Hands messaging strategy: directly acknowledge Q4 revenue miss, then pivot to optimistic outlook highlighting $22M H1 pipeline and unified GTM plan. Peter to present tech updates (service endpoints, Nerf) and guide Mural board walkthrough. No naming specific deals to avoid premature expectations.
Conference Travel Approval - David Godlove HBCSF
Approved David Godlove travel to speak on Apptainer at HBCSF conference in Chicago in late March (~$2,200 cost). Required Chris Wolford to coordinate with Lindsay (Marketing) and Chris Baek (Finance) as part of the approval.
Strategic Map Framework - Value Drivers vs Internal Efficiency Separation
Established new H1 strategic planning framework that separates customer-facing Value Drivers from Internal Efficiency Drivers. Framework uses three lanes: middle lane for Value Drivers (the WHY), top lane for GTM activities, bottom lane for engineering deliverables. Also established phased estimation process: low-confidence ballpark dates first, then engineering-only session to raise confidence.
Marketing ICP Validation - Collaborative Research Approach
Pushed for marketing to validate ICPs with real data rather than just executing on what was decided in the planning room. Established that ICPs are hypotheses to test, not fixed targets, and Lindsay has permission to explore outside defined ICPs if data warrants.
Partner/User Management Tech Debt - Accept for Speed
Explicitly acknowledged and accepted that Partner Portal, Fuzzball SaaS, and Portal Depot will have separate user/account systems rather than integrating them. Flagged the future cleanup cost but chose speed over architectural purity.
Commitment to Present Engineering-to-GTM Messaging Framework
Committed to presenting a framework next week that ties engineering work to changes in market state and corresponding go-to-market messaging. Triggered by Fuzzball Service Endpoints press release that was 98% HPC-focused, missing the critical AI angle despite AI being the strategic priority.
Related Patterns (6)
Executive Sponsorship for Strategic Partnerships
Strategic cross-company initiatives and major client partnerships require executive-level accountability to move at the right pace and ensure proper prioritization.
Small Circle for Sensitive Operations
When executing sensitive strategic operations, keep the circle of informed people as small as possible to prevent leaks that could accelerate hostile action or undermine the initiative.
Protect Engineering Capacity
When external demands threaten to overload engineering capacity, protect capacity by either requiring the demand to come with additional resources, or forcing hard prioritization choices upstream.
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.
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.
Conscious Tech Debt for Execution Speed
When facing time pressure, explicitly acknowledge and accept technical debt rather than blocking progress. The key is making the trade-off consciously and visibly so it can be addressed later.