habitatchronicles.com/2004/04/you-cant-tell-people-anything/, posted 24 Jun by peter in cognition management people
What’s going on is that without some kind of direct experience to use as a touchstone, people don’t have the context that gives them a place in their minds to put the things you are telling them. The things you say often don’t stick, and the few things that do stick are often distorted. Also, most people aren’t very good at visualizing hypotheticals, at imagining what something they haven’t experienced might be like, or even what something they have experienced might be like if it were somewhat different.
You need two things to effectively move fast: a culture of psychological safety and smart investments in tooling. Employees need to feel empowered to speak up if things are moving too fast—if they are concerned about why a feature is being built and to identify gaps in the processes. They need to feel they won’t be blamed when something breaks. Building this requires empathy, open communication, and teamwork. This psychological safety is the foundation of being able to move quickly and quickly recover when things break.
Next up is selecting the right tooling and processes. Invest in tools that make things easier. Tools should be useful, usable, and change the underlying problems, not create more.
Time is seen in a particularly different light by Eastern and Western cultures, and even within these groupings assumes quite dissimilar aspects from country to country.
https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory, posted Feb '20 by peter in agile continuousdelivery development management
I’ve used the term *Feature Factory* at a couple conference talks over the past two years. I started using the term when a software developer friend complained that he was “just sitting in the factory, cranking out features, and sending them down the line.”
How do you know if you’re working in a feature factory?
https://www.objectstyle.com/agile/why-developers-hate-agile, posted Oct '19 by peter in agile development management opinion
Many developers have been voicing their concerns about Agile being broken lately. Among them are prominent figures like Robert C. Martin and Kent Beck – two of the people who charted the Agile Manifesto. Some of the most frequently-mentioned problems with Agile are: Agile ignores technical debt; frameworks like Scrum are just “red tape,” which they were never supposed to be; programmers are asked to commit to arbitrary estimates and deadlines and never get the time to think thoroughly about the features they’re creating. So if we can acknowledge and work on these problems, perhaps we can fix Agile.
https://psmag.com/social-justice/confident-idiots-92793, posted Oct '19 by peter in cognition management science
But here is the real challenge: How can we learn to recognize our own ignorance and misbeliefs? To begin with, imagine that you are part of a small group that needs to make a decision about some matter of importance. Behavioral scientists often recommend that small groups appoint someone to serve as a devil’s advocate—a person whose job is to question and criticize the group’s logic. While this approach can prolong group discussions, irritate the group, and be uncomfortable, the decisions that groups ultimately reach are usually more accurate and more solidly grounded than they otherwise would be.
For individuals, the trick is to be your own devil’s advocate: to think through how your favored conclusions might be misguided; to ask yourself how you might be wrong, or how things might turn out differently from what you expect. It helps to try practicing what the psychologist Charles Lord calls “considering the opposite.” To do this, I often imagine myself in a future in which I have turned out to be wrong in a decision, and then consider what the likeliest path was that led to my failure. And lastly: Seek advice. Other people may have their own misbeliefs, but a discussion can often be sufficient to rid a serious person of his or her most egregious misconceptions.
Interesting article written by David Dunning, of Dunning—Kruger effect fame.
When you are solving a difficult problem re-ask the problem so that your solution helps you learn faster. Find a faster way to fail, recover, and try again. If the problem you are trying to solve involves creating a magnum opus, you are solving the wrong problem.
https://www.yegor256.com/2015/07/13/meetings-are-legalized-robbery.html, posted Jun '19 by peter in business management opinion people
A good software architect, as well as a good project manager, doesn’t need meetings and never organizes them.
Meetings demotivate, waste time, burn money, and degrade quality. But more about that later. For now, let’s discuss a proposed alternative.
timharford.com/2019/06/why-brilliant-people-lose-their-touch/, posted Jun '19 by peter in business cognition management people
This is not to say that skill doesn’t matter — merely that in a competition in which all the leaders are highly skilled, randomness may explain the difference between triumph and failure. Good luck plus skill beats bad luck plus skill any time.
www.bbc.com/capital/story/20190514-taking-a-more-outlandish-approach-to-workwear-could-pay-off, posted Jun '19 by peter in business management people
Standing out, rather than fitting in, could in fact be the smarter route to success. A phrase coined in a study published in the Journal of Consumer Research in 2014, the “red sneaker effect”, revealed we confer higher status and competence on mavericks versus conformists.
So we often perceive someone wearing clothing that deviates from the norm in professional settings as having higher ability, rank and respect than colleagues who conform to dress codes.
This is because diverging from the norm signals you have autonomy and can bear the cost of nonconformity – even if it costs you your job.
But she found that in collective cultures,such as East Asia and Latin America, people prefer norm followers as leaders, because they may prioritise organisational goals over their own.