Earlier quoted context omitted.
The problem is that many people believe "empowerment" means "do whatever the fuck I want." At any company you are going to have objectives and goals, and empowerment means getting the responsibility to make the hard trade offs yourself. It doesn't mean you can do something outside of the corporate goals, and it doesn't mean you can just ignore some of the challenging parts of the job like delivering a working product…
The problem is theres's no natural distinction between "what" and "how." Every aspect of how you do your job is meaningful in some way. You have to have a good understanding with your boss about where you have discretion to follow your judgment and where you don't.
The first non-bullshit book about culture I've read
71–80 of 156 posts
Re: The first non-bullshit book about culture I've read
#72My experience as a Development Manager for the past ~year (YMMV): 1. I'm playing chess; senior management is playing checkers. No, not because I'm some sort of genius and they are simpletons, but rather they talk about interchangeable "resource units" and I know these FTE's as "Tom" and "Amy", each with specific strenghts and weaker areas. Big strategic plans cannot differentiate but we front-line managers need to fi…
Re: The first non-bullshit book about culture I've read
#73My experience as a Development Manager for the past ~year (YMMV): 1. I'm playing chess; senior management is playing checkers. No, not because I'm some sort of genius and they are simpletons, but rather they talk about interchangeable "resource units" and I know these FTE's as "Tom" and "Amy", each with specific strenghts and weaker areas. Big strategic plans cannot differentiate but we front-line managers need to fi…
Can you supply some examples of good goals? Thank.
Re: The first non-bullshit book about culture I've read
#74My experience as a Development Manager for the past ~year (YMMV): 1. I'm playing chess; senior management is playing checkers. No, not because I'm some sort of genius and they are simpletons, but rather they talk about interchangeable "resource units" and I know these FTE's as "Tom" and "Amy", each with specific strenghts and weaker areas. Big strategic plans cannot differentiate but we front-line managers need to fi…
Re: The first non-bullshit book about culture I've read
#75Re: The first non-bullshit book about culture I've read
#76Earlier quoted context omitted.
> then a slow die-off until the next book. I'm curious if you think that it's actually possible for a book (or perhaps more generally, a school of thought) to actually break out of the cycle, or whether it's just the natural order of these sorts of things. What I mean is, maybe what we get from these sorts of "self-help" pieces of literature/philosophies/whatever is less like a mantra that's one and done, and more li…
Like you describe, I just kept sucking it all in, consuming as much as I could. I have self-taught through a few of these subjects. I don't have an answer for you, but I have an answer for me. Perhaps sharing my answer might help you too. I hope so. These are unsolved problems, that's why the material keeps getting produced. I think if you can find inspiration or a good "nutritional meal" to last for a while, it's a…
Every book gives advice, every advice is an answer to a question. Ignore the answer, but scrutinize the question.
For example: "embrace remote work, go remote-first even!" says one book, "face-to-face is the only thing that works in the face of inevitable confusion and complexity" says another. Not helpful, right? However, consider that the first author got good result with remote work, and the second one got great results in-office. The two may have had different circumstances which they fail to describe for the reason you're describing the air you are breathing - being very immersed in something makes that something invisible. So a question to ponder then: under what circumstances is remote work possible, and if/how can one modify those circumstances?
Scrutinizing the question is a lot more work than getting excited with the first answer that came your way, but it's that much more likely to yield applicable result on top of a bout of enthusiasm.
Also, thanks for [The Culture Code: The Secrets of Highly Successful Groups] suggestion.
Re: The first non-bullshit book about culture I've read
#77Does anyone have book suggestions on leadership and management which aren't just pop-business BS?
Skip the business books and just study the lives of great leaders. Personally I recommend Napoleon, Orson Welles, Kurosawa, Fellini and Hitchcock. Basically anyone that was consistently productive in a group-based endeavor.
Re: The first non-bullshit book about culture I've read
#78Turn the Ship Around!: A True Story of Turning Followers into Leaders, by L. David Marquet
Also here's a great speech given by the David Marquet (with drawings!) on the same topic:
Re: The first non-bullshit book about culture I've read
#79Earlier quoted context omitted.
> This reads like a commercial, but I'm not going to downvote it Is it possible to downvote a submission? I thought you could only upvote and flag?
When your internet points on HN exceed some threshold you may be able to downvote. I’ve heard there’s also a thing called a supervote. (I have neither of these privileges)
Super down voting is something only mods can do (maintains the story, but it gets nuked off the site index)
Re: The first non-bullshit book about culture I've read
#80To some extent, I'm no longer curious about "leadership" ideas about organisational culture. I understand that culture counts for a lot, but modern organisational cultures are getting complaints that "leadership" is not going to solve at scale. Maybe motivation/attitudes can be improved and a naval hierarchy can work better, but this is not the typical issue in corporate culture. I'm curious about structural answers.…
>I understand that culture counts for a lot, but modern organisational cultures are getting complaints that "leadership" is not going to solve at scale. I'm not sure if I agree or disagree with you - on the one hand, this statement seems wrong, but on the other hand, everything else you said makes a ton of sense to me. Everyone seems so caught up by culture these days that they forget the other big part of the leader…
For example, I had a situation where I had a story to write functional tests for a piece of our software. The story's scope had creeped (there turned out to be disagreement between different levels of leadership over what the tests should cover), but I had reached a point where I had implemented roughly 80% of the tests that we needed. I submitted a pull request for the progress that I had made so that it could be "locked in" and I could get it out of my mental overhead. However, the person who reviewed the PR refused to merge it because we apparently had a policy that each story could only have one PR. Ultimately, the overhead of trying to get everything in all at once resulted in the story not being successful.
Although maybe that example illustrates your point about the importance of process, because I had been asking for weeks for us to actually have sprint planning so that I could break up the story, but it kept getting canceled because people felt that they were too busy.