Art
Dec 24, 2025 - Jul 10, 2026
3
Decisions
0
Active Todos
2
Patterns
Categories
Decisions (3)
Rule the Toyota kernel patch a feature not a bug; no automatic queue jump, escalate through normal priority
Nathan flagged a Toyota/Yoshi request (relayed via Art/sales) framed as a bug fix. Peter ruled it is a feature, not a bug, so it does not automatically jump the engineering queue on the bug argument. Support may still be offered, but the bug framing is off the table. If the business wants it prioritized it must go through normal escalation and trade-off (Peter + Bjorn), not a backdoor via mislabeling severity. Reinforced later the same day in the Ryan 1:1 (Peter rebuked Art for taking the bug-vs-feature fight to engineering).
Toyota POC — No Hotfix, Demo MPI and PBS Separately
Decided NOT to rush a hotfix for Toyota's urgent out-of-scope MPI-via-PBS request before their Thursday director meeting. Team will demo MPI and PBS as separate working components, explain the integration bug is known, and commit to fix in ~1 week by the March 17 Reno meeting.
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 (2)
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.