Someone smart who knows something wants to add it and gets tangled up in "useless" beaurocracy. Why can't they just let me do it!?
Because if they did just let people do stuff, then lots of other people you consider idiots would have already done things you consider stupid and or bad.
Basically everyone wants rules for the idiots so they don't ruin things and at the same time to not be included in the list of idiots.
That would sound harsh though, so mostly people just moan about rules, rather than them not being exempted, but I don't think anyone genuinely wants the rules to be dropped for everyone.
For example, consider two smart Wikipedia editors working on the climate change and global warming pages... one from the fossil fuel sector, one from the renewable energy sector.
2) If she exists, and is as smart as she should be, she will realize quite quickly that her power can be used for personal gain and she will become corrupted. Power corrupts, etc. and you can't really entertain any kind of organizational solution without considering game theory of the situation.
The problem is not rules/"idiots"/novices. The problem is when people who make/enforce the rules are not fit to do so, cling to the rules and apply them with sweeping generality. The people who create those problems are typically incompetent but eager or even zealous at the same time.
They are resistant to learning, addicted to power and/or afraid of change and certainly afraid of appearing incompetent. So they never get past that level where they start to recognize when rules need to change or need to get broken.
Ask me to navigate a bus station in a provincial Chinese city and I'm a complete fucking moron though. Ask me how I know.
Point being, there's no such thing as idiocy without context.
Exhibit A: me writing ;p
> we have multiple on differing levels of the idiot scale depending on the topic at hand
or even depending on the time of day, or current stress/work levelsalot of things can affect the idiot scale...
You need some brakes on the organization to assure that the rate of change is manageable and that marginal ideas are implemented more slowly if at all.
It might also be better to have a much faster pace and more freewheeling "default don't care; if you can make it work, it'll stay" which also then requires a relatively ruthless culling mechanism (even if slightly unfair) for the things that don't work.
It would seem fairly easy for Wikipedia to examine its own pages for broken links and flag any such link (and its related content) as unreliable. Wonder what that would look like...
(If they are not succeeding, they can't afford to hire a consultant, of course)
It's my firm opinion that there is a U shaped curve of chaos - new companies do not yet know what they should be doing to make money, and large companies are inherently too complex for any one person (or subset of people) to actually understand what is happening.
This is why I prefer to work with and for medium sized companies - companies that can have goals and metrics that lead to success, but are not yet so large that they are inherently unknowable.
Feedback loops of communication is what I view as the biggest inefficiency. If you CC 10 people on an email, you’ll still be chasing 3 of them for a response next week.
Out of curiosity, how do you define a medium sized company? How many people, how much revenue, etc? The way people define this varies widely, so just trying to understand how you define it.
In startup terms? Private companies, usually post Series A (usually B or C) but not yet private equity unicorn rounds. In market cap terms it's 100m+ to <2b or ARR ~2m to ~25m for a sass-style company. still a "small cap" in the grand scheme of things.
I’m reminded of SpaceX, who is run by Gwynne Shotwell and Elon Musk. Gwynne keeps the whole business machine running and manages existing programs so well that Elon has the bandwidth to dig down to a fractal level and address a lot of the weird issues & bottlenecks that everyone knows about while leading new programs extremely fast. Or at least, that’s the story (doubtless the CEO meddling has negative effects, too, but overall seems to work at least as well as traditional organizations that big). Also, maybe that can only happen in a business like SpaceX which is filled with a bunch of fantastic workers who are just really driven to make things work at all levels.
I fantasized about what if there were some kind of internal company web app, a portal or dashboard, where people at the highest levels, if they cared (I am not even if sure they did), could drill down to a "fractal level" (as you called it) and see what the software is actually coded to do, presented in a way that makes sense to a non-programmer/higher-level understanding.
The elevator pitch for this kind of IT product would be: "Software runs your business, and you don't know how it works."
Unfortunately I never could figure out how to actually turn this into a real thing. None of the common approximations of software (modeling) do a very good job of capturing subtle aspects or of being more understandable than the code itself. The one conclusion I did come to is that it would have to be something where low level developers interpret and model the code to digest it for whatever format the portal uses, and not some kind of automated distillation or analysis of the code.
I think it might in fact be impossible but if you ever figure it out you'll win all the marbles.
Your target customers might end up being other programmers or managers though.
So people are inherently skeptical, and by the time it becomes obvious that they need some outside heavy hitter, it's too late for that strategy to be effective.
I'd really like to systematize it, to be known as the solution for that kind of problem, but that's a different skillset than actually solving the problem, of course.
its not like the solutions are usually that hard to figure out, it's always a problem with people and their incentives ultimately.
the fixer role is basically to give confidence to the CEO that disempowering certain people is safe and there's a path out.
SpaceX Falcon 9 and Falcon Heavy vs Vulcan and New Glenn and Ariane 6.
SpaceX Starlink vs OneWeb.
SpaceX Dragon Crew vs Boeing Starliner.
SpaceX Starship HLS vs Blue Origin HLS.
Even if the optimum is somewhere in the middle, the middle region is a spectrum and the part you picked might be worse than the ends. (Picture a sine-wave shaped graph of quality vs size.)
No, this requires you to constantly steer left (or right, of course). So you are not traveling on a straight line.
[0]https://www.technologyreview.com/2018/04/30/143150/computer-...
A large enterprise such as Google, GE, or IBM can be poorly managed for decades before being economically forced to change.
I observed a team making 25 MM per engineer in a large company that made one change per year. There are products at google that require 400+ pages of documentation/proof to change.
On the other hand in these orgs you have people crying "iceberg!" all the time.
Well at least operationally it was a good product, and imo better than Netflix's, but I have no idea if helped or hurt them financially.
But Blockbuster's established sources for content/disks should have been an advantage against the stories of Netflix having to go buy retail copies of movies in cases of uncooperative distributors.
It was just Phase 2 and moving to streaming where they fell so far behind. (Plus Redbox's uprising didn't help, which is a separate failure to pivot.)
But failing can be good and bad.
https://www.ribbonfarm.com/2009/10/07/the-gervais-principle-...
Sociologists have quantified these sorts of relationships almost a hundred years ago with graphical modelling.
And thereby deliberately push it into dysfunction. At least when seen by an impartial observer.
It is easy to nag when they never had to secure anything or operate at scale of 100's of employees and 1000's of users.
It is just hard even if you have good practices in place, because checking that everything is in place and training new people to follow rules is a lot of work.
Once you have a large org that's making money, you don't really know exactly why it makes money. Sure, there's annual filings and there's still the elevator pitch of what the org does. But the actual how of how it works is difficult to describe in causal terms: if team X or Y was not there, the business would do better/worse? How does this team interact with that? It's really a bunch of informal relationships between different people, and both the people and the relationships change over time.
So what you want to do when you know the whole sorta-works and you want to keep it that way is you pour glue all over it. You try to formalize processes, you give people titles and you make hierarchies. That way you attempt to stop the firm from inadvertently slipping into dysfunction.
The side effect is of course that everyone who works there can see ways to improve things, but they can't see a way to get those improvements implemented.