Brian
hey, quick sync on the release?
Jake
if this is about moving the deadline again, I'm not going to like it
Brian
not moving it… just adjusting scope slightly
Jake
"slightly" usually means a lot more work for us
Brian
it's just one more flow
Jake
one more flow = backend changes, QA, edge cases… you know that
Brian
leadership wants it in this release
Jake
leadership doesn't have to build it
Brian
they do have to answer to clients
Jake
and we have to answer for bugs
Brian
we can't keep saying no every time
Jake
we're not saying no, we're saying not now
Brian
timing matters, Jake
Brian
competitors are already shipping similar features
Jake
rushing just to match them is how we break things
Brian
or how we stay relevant
Jake
we're not irrelevant
Jake
that sounded like a threat
Jake
reality is we're already stretched
Brian
then help me find a way to make it work
Jake
we already gave you a plan
Brian
a plan that doesn't include this feature
Jake
because it didn't exist when we planned
Brian
this came from the top
Brian
I'm trying to balance both sides here
Jake
doesn't feel like it
Brian
what would it take to include it?
Jake
either more time or fewer features
Brian
we don't have more time
Jake
then we cut something else
Brian
everything else is committed
Jake
then be honest with them
Jake
that we can't do everything at once
Brian
that's not what they want to hear
Jake
it's what they need to hear
Jake
you can push us, Brian
but physics still applies
Brian
and you can block things, Jake
but business still moves
Jake
then decide what matters more
Brian
we're adding the feature
Jake
then you're also adding the risk
Brian
I'll take that call
Jake
no… we'll take that hit
This is where the conversation ended
The feature shipped three weeks later.
Nobody checked if it was stable.
Rate this conversation