6 ms·
In most companies I've worked, in order to actually implement an idea, you need to prove a few things, whether the person proposing it is the PM, an engineer, o
by ryandrake 2y ago
In most companies I've worked, in order to actually implement an idea, you need to prove a few things, whether the person proposing it is the PM, an engineer, or any other person involved in the product:
1. The idea is technically feasible
2. The idea aligns with company's business goals
3. The idea is our team's responsibility and cannot be done by another team
4. The idea is more important than the other things our team plans to work on in the future
5. The idea is more time critical than the other things our team is working on now
If any of these cannot be proven, then it goes on the backlog as a P4 and nobody realistically will ever look at it. It's just the reality of corporate software building. There are always 10-50x more ideas than there are staff/time to work on.
Of course, all five of those can be, and often are, overridden by the Prime Directive:
0. One of the executives (often one of your grand-bosses high up on the totem pole) wants it.
- p1necone 2y agoIn my experience the more fine grained an organizations issue tracking/planning is the more this is a problem vs a reasonable process. If you have to convince someone of all of those things in order to build some reasonably large thing over the space of a few weeks, that's probably reasonable. If you have to convince someone of all of those things in order to allocate a few hours to fixing some tech debt or minor bug then your codebase is going to slowly deteriorate until the same someone is asking you why there's so many bugs and everything takes so long to develop.
- elevatedastalt 2y agoUsually most engineers have some slack time and can pick things up to fix. The problem is not in them doing that. The issues arrises in one of two things— [1] They either use the fact that they are fixing that thing as an excuse to not work on or deliver on time a different, more important task. If that happens, obvious questions about prioritization occur. [2] They want a substantial amount of credit or recognition for doing it. Usually such fixes don't receive exec attention (since execs are tracking more important projects) and so don't get the same due as a properly tracked project does.
- wbl 2y ago3: the fix is easy but the integration testing and deployment cannot happen without allocated time.
- titusjohnson 2y agoIn my experience this aspect is chronically underestimated by devs. The change needs testing. Change Management might need to create artifacts. Help articles might need updating. Certain clients may need a heads-up. All the PMs need to be briefed (this change is outside of their roadmap so it'll be a fun surprise). As an org grows the piece of the Effort Pie that is Development gets smaller and smaller. It's not that development gets easier, it's that every other part of the process grows in size and importance faster than the Development piece grows. It takes about an hour of developer time to incidentally produce 20 hours of work elsewhere in the company.
- deleted 2y ago[deleted]
- Dylan16807 2y agoIf it meets 1-4 does it get forgotten or does someone reliably come back to check for 5 becoming true?
- joshuanapoli 2y agoProbably the person who came up with the idea remains the most invested in it, and they should to watch for number 5 “the right moment” to bring it up again.
- psunavy03 2y agoOr you work at a non-software company where the technical folks ultimately report to a non-technical boss, or are outnumbered by nontechnical executives. In which case, there's the real danger of a bunch of 0 getting shoved down your collective throat to the tune of "it's all a priority, get it done."
- asoneth 2y ago> "it's all a priority, get it done." Reminds me of a product owner I had who abused priority categories by insisting that the majority of his tasks were "top priorities" because he had discovered that any time he didn't mark a task as a top priority it wouldn't get done. Every team ended up sorting his tasks as a flat list so that when he asked people to "make this a top priority" it was up to him to decide where it went in the list and which of his other requests would get bumped.
- skydhash 2y agoThat reminds me of a technique in the Slow Productivity book by Carl Newport. The gist is, if you cannot control the flow of work, the best thing to do is to create a buffer and make the workload visible. So they can visualize how any new task is going to disrupt it.
- dyarosla 2y agoAlso, but rarely: Some engineer wants it bad enough that they just build it -or some version of it- and then some executive gives the go-ahead to invest more into it. At the end of the day, ideas are just ideas. Execution is everything.
- 3vidence 2y agoI've learned the value of this. Some people don't realize the value of something unless you show it to them. It's a risk for sure but honestly it keeps me sane vs trying to get 10 people aligned before starting something and then running out of time. People will happily take credit for your work after it works.
- unkulunkulu 2y agoyep, an engineer has the power to directly influence the code. This is a strong power. Sometimes just making a PR is enough and a good convincer in and of itself. Use sparingly of course, weigh in time for making the argument, but this is an artifact just as a convincing research, text or a plot. code can be part of the argument.
- sfn42 2y agoI once worked on an application that integrated with a third party api. The way it did this was with a large and horrible client library that used a separate db to cache the data. The data was then fetched from the main application and used to rebuild the pages (in the main db) based on this data once a day. The library had lots of problems, and one day it stopped working. I was tasked with fixing it - we had the source code, it was purchased from someone and copied into the repo. I spent most of the week if not more trying to figure out what was wrong, but I couldn't. What I did learn was that this library was some of the worst most pointless code I'd ever seen. So I told the team that I think I can rebuild this thing from scratch faster than I can fix this bug. The intermediate db is pointless and most of the library code is dead, the rest is garbage. I can make a simple little thing that does exactly what we need better, faster and easier. Nope. No bueno, fix what we have. So I spent a few hours over the weekend, less than a workday, building the new solution. Come Monday I had it pretty much working, a few things needed to be done but it already supported the use case. The pages were built correctly, they had the necessary content but some things were a bit messed up, nothing difficult to fix. Showed it to the team, said I want to use this and delete the old stuff - nope. The only half-decent explanation I got was that the client had paid a way too high amount of money for this garbage library and I guess the team lead didn't want to tell them we wanted to throw it out or something like that.
- thaumasiotes 2y ago> 3. The idea is our team's responsibility and cannot be done by another team Is it really true that your company cannot implement any idea that could potentially be done by more than one team?
- droopyEyelids 2y agoIf more than one team could reasonably be the owner of something, -and- the ownership isn't going to get a manager promoted, there needs to be a showdown to see what team takes the impact to their roadmap