←back to thread

Splitting engineering teams into defense and offense

(www.greptile.com)
210 points dakshgupta | 1 comments | 14 Oct 24 20:07 UTC | HN request time: 0.203s | source
Show context
jph ◴[14 Oct 24 21:00 UTC] No.41841941[source]▶
Small teams shouldn't split like this IMHO. It's better/smarter/faster IMHO to do "all hands on deck" to get things done.

For prioritization, use a triage queue because it aims the whole team at the most valuable work. This needs to be the mission-critical MVP & PMF work, rather than what the article describes as "event driven" customer requests i.e. interruptions.

replies(2): >>41842129 #>>41847978 #
Kinrany ◴[15 Oct 24 12:43 UTC] No.41847978[source]▶
You're not addressing the issue of triage also being an interruption.
replies(1): >>41853198 #
1. jph ◴[15 Oct 24 21:13 UTC] No.41853198[source]▶
A triage queue can include how/when to do triage. As a specific example, set 60 minutes each Friday to sift through bug reports together. Small teams with good customers can reply honestly with "Thank you for your bug report. We're tracking it now at $URL. We expect to look at it after we've shipped $FEATURE. If we've misunderstood the urgency or severity please call us directly at $PHONE."