HI version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
90% Positive
Analyzed from 875 words in the discussion.
Trending Topics
#don#organizations#https#com#slides#google#slime#authority#team#doesn

Discussion (20 Comments)Read Original on HackerNews
Many tools are available today to alter data representation. And frontier LLMs have high fidelity. You don’t have to wait for someone to help you. Claude helps those who help themselves.
1. Visit the embedded google slides URL https://docs.google.com/presentation/d/1XMCU2vxtxxqqQ2NY567n...
2. Click File
3. Scroll down to 'Download' and point your cursor at it and wait for the submenu to open
4. Select PDF Document
5. Upload the PDF Document to your chat agent of choice
Not everyone is able to type the following and get results, but I'm built different:
> Summarize this for me: https://komoroske.com/slime-mold/
> It’s a google slides thing but i don’t want to click through
Here. Scroll bar included so you can see it's literally the only prompt https://imgur.com/a/Qela4qt
I think the ideas are solid but it's the C-suite that needs to deal with this and rarely cares. In other words, it's about organizational culture.
Usually they are structured in ways that can be gamed and the structure is defined by those that benefit most from them being gamed.
But then again, this is a view from the underbelly of corporate life and I may be missing something.
An autonomous team that does what they are told or an autonomous team is free to pursue opportunities as they see fit are both useful and can react quickly. The question is how much scaled alignment you need to execute a particular goal.
You can’t invade a country with one squad of 10,000 soldiers or 1,000 squads of 10 that do as they please. You need to delegate execution authority to small teams who are aligned to a shared goal.
Similarly, you can’t expect one group 10,000 devs with no internal structure to explore and find interesting opportunities to explore; you’ll just get noise. Nor can you try to manage 10,000 devs directly. You won’t be able to grok the context.
Complexity management in organizations follows the same patterns as in code. Single responsibility, don’t repeat yourself too much, encapsulation, etc.
It’s really a function of information theory, the more people you have to ramp up or keep current on context, the lower your ability to make and stick to decisions.
I don't think the author is really super familiar with some of those other organizations he mentions so he's reflecting how he thinks they work rather than how they work. That said the observations are still pretty good.
> You need to delegate execution authority to small teams who are aligned to a shared goal
It's been a while since I read the slides but this is basically what the author is advocating for and what doesn't tend to happen in dysfunctional organizations.
> Complexity management in organizations follows the same patterns as in code. Single responsibility, don’t repeat yourself too much, encapsulation, etc.
There are a lot of parallels. But organizations have people so that's an extra factor. You can't just "refactor" them without thinking about people's egos, objectives and such. So a lot of thought is needed into how to build effective organizations and sadly not enough thought is given is most companies.
Agreed the observations are interesting, and that’s what is being advocated for, I just don’t think top-down vs bottom-up is the axis that impacts that as much as disturbed vs… I said “centralized” but probably “localized” is a better term.
These are two public previews that we are building off of for the journal:
1. https://paragraph.com/@hq.spengrah/an-actionable-model-of-tr...
2. https://x.com/hatsprotocol/status/1986458735095517526
Funnily enough it’s extremely relevant to agents/subagents.
A substantial portion of company goals is set by a very small group that is far removed from the day to day work, and the goals are often connected to timelines and financial expectations well before any team member gets into the project.
To have slime mold like behavior, a corporation would have to hire employees, give them time and resources, and general guidelines and goals, but let specific targets and projects bubble up.
This is fundamentally incompatible with a next-quarter profit driven corporate financial structure.
https://www.youtube.com/watch?v=KfbLSl_4o78