|
|
|
|
|
|
by satyan
5838 days ago
|
|
|
@RiderOfGiraffes The write-up is about a bottom-up approach in making organizational decisions. Most of the decisions as we know are made right at the top, with minimal understanding of what people on the ground are actually thinking about. Once you start listening to your people and pick your organizational directions from there, the whole decision making process gets more efficient. Keep the floor open for different kind of discussions. Keep looking at what discussions are catching heat (more people talking about it). Pick your directions from them. That was the intent. Eg. Which technology is the most popular among our folks? What kind of clients are liked by our folks? What kind of work do our people prefer? etc. etc. |
|
|
* Why didn't you write that?
* For these sorts of decisions, why not empower the employees to do things without requiring decision/dictats from on high?
* Most "chat" in forums like the ones you seem to be suggesting are a genuine, complete waste of time, and ...
* Most proposals from "the floor" have been really, really poorly thought through, and just won't work.
Now, let me say that I agree with what you're trying to accomplish, and that your comments/thoughts have some merit, but as they stand they seem poorly thought through and unimplementable in practice. I'd really like to see you have something more concrete and practical to suggest that solve the problem you think you've seen.
I manage a company with around 30 employees - not real big, but the sort of shop where your ideas might be relevant, especially to implement them before we get any bigger and change is harder. However:
* Which technology is the most popular among our folks?
We let them use whatever technology they want, provided they can then justify their decision. We empower our people to make decisions and stand by them.
* What kind of clients are liked by our folks?
We don't have a choice as to our clients. We have multi-million dollar contracts in a fairly small market.
* What kind of work do our people prefer?
I don't understand how that kind of question can be made relevant. Our database people work on database stuff, our embedded people work on the embedded stuff, our user experience people work on user experience stuff, and everyone talks to everyone else, because all of the software modules talk to all the other software modules. If a database programmer wants to work more on the embedded side then he studies up on his own, asks for some tasks, gets given some tasks under supervision, then his skill set is bigger and the task allocations can be more favorable to him.
In short, it sounds like you're sounding off without really thinking about how things really work. I'd like to see a better, more thought through presentation.
Finally, it might sound like I'm attacking you, or picking on you, but I am genuinely interested in any ideas on how better to manage. I'd hoped there was something interesting in your article, I feel like there's a hint of something interesting in your article, but then it all went away and feel like I was left with nothing.
If there's more, write it better.