Dave Dickerson
Dec 24, 2025 - Mar 6, 2026
5
Decisions
0
Active Todos
6
Patterns
Categories
Decisions (5)
Custom Engineering Scoping Process — Nathan as Gate
Established formal process for unplanned custom engineering requests from sales: Nathan provides quick effort estimate (days/weeks/months), enabling formal prioritization. Nathan can say no, escalation goes to Peter.
New Engineering Mandate - 2x Velocity in 6 Months
Set new mandate for Justin and Nathan: top priority is building a team that can deliver twice as fast in six months. This is a shift from the previous coaching model to a performance-driven one - setting ambitious targets, holding people accountable, and replacing underperformers.
Everfox partnership requires ARR-target-level contract to proceed
Participated in technical scoping meeting with Everfox to understand feasibility of supporting their RHEL 8 to RHEL 10 migration for 100k+ hardened thin client units. Meeting was exploratory - no commitment made.
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.
ProServe Work Prioritization Process
Established new process for handling professional services work: ProServe work will be prioritized against existing roadmap, not by dropping in-flight work. Product (Brady) owns prioritization decision, Engineering determines timing based on capacity.
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.