4 ms·
Yeah, you have to discuss your issues with the additions. If they are non-technical then you can make up some story about the world exploding if they go through
by md1515 15y ago
Yeah, you have to discuss your issues with the additions. If they are non-technical then you can make up some story about the world exploding if they go through with it...
...I'm a non-technical co-founder and I DO micromanage, but I keep an open mind if my programmer says it is more difficult, harder to implement etc. We have a good relationship with that type of stuff. Marketing/business people have reasons for where they put buttons etc., but you need to get on the same page with him about projects that can't be added.
- gyardley 15y agoIf they are non-technical then you can make up some story about the world exploding if they go through with it... Yeah, don't do this. Eventually even a non-technical person will figure out he's being bullshitted, and then you end up with a guy who doesn't trust you (for good reason) and often developers as a whole.
- fatalerrorx3 15y agowhy DO you micromanage? It puts unnecessary pressure on the people involved and it causes a significant loss in productivity, I had a hard time sleeping last night because of it...no one being micromanaged is going to be as willing to discuss their ideas with you, no matter what kind of open relationship you think you have with them, it makes them feel bad about themselves and their work
- md1515 15y agoWell I micromanage in the sense that a button location will be changed if I have a purpose. A font will be changed if I have a purpose. A function will be perfected if it serves a purpose. Like I said, everything I ask will serve a purpose and I will explain that purpose to the programmer and we will discuss what we think is best. Nonetheless, I'll keep that in mind..