4 ms·
A few important lessons here. You dont tell someone NO. You say, I could do this, or I could make this change and it would work in a standard way. If you want
by zer00eyz 2y ago
A few important lessons here.
You dont tell someone NO. You say, I could do this, or I could make this change and it would work in a standard way. If you want me to do it this other way, I can but it is going to cost XXX extra hours to build it, and probably incur a lot of future work to maintain our own "version" of this.
Then when they say "do it that way" you go into your planing meetings and say "task xxx is 2x longer for a design deviation"
Make sure if you say this, it goes in an email. You know why all the old people send you emails for bullshit? Because we have all been burned and know that we can keep copies of that for CYA reasons.
I didn't see an email (a lot of them) is a bad excuse 6 months down the road. When the bills come due and the design team is getting a beat down.
- SavageBeast 2y agoConsulting 101 training kicks in here - YES is always the answer to any request, followed by "heres how long it will take, how much it will cost and what other priorities will need to be shifted. We can get started this afternoon if you're good with that?" Stakeholders asking for crazy things back up real fast when you take their requests/demands/GOOD IDEAS and apply these realities to them.
- FLAMEDEV 2y agoMost of conversation are on open channel. For them it's like, you think it's difficult, park it for later and do it later. But they don't update the designs.
- zer00eyz 2y ago> Most of conversation are on open channel. This is the hallway of modern Remote work. You either do it right and pay the price or the design gets updated... Email shit, make a point to keep asking the question till they reflect whats going to get built. Deisgn is an implementation detail, not a cost driver. You aren't working for apple.