This guy coaches Sam Altman.
He also works with leaders at Anthropic, Google, Apple, and SpaceX.
I sat down with him to learn how he coaches billion dollar businesses.
Here are Joe Hudson’s 7 operating rules:
1. Kill your 1:1s
These meetings lead individuals to solve problems instead of the team. Much better to bring problems to the whole team so everyone feels responsible for solving them. I agree, haven’t done them for years...
2. Rotate who runs recurring meetings
When the same person always leads, people focus on pleasing or rebelling against them. Spreading the authority makes everyone accountable to the team instead.
3. Give anyone the power to change a bad meeting
Everyone already knows when a meeting isn’t working (and usually why). Giving people permission to say it makes meetings more effective.
4. Make every employee run at least 5 experiments a quarter on their own job
It makes the team more productive, keeps people interested, and helps retain smart employees who would otherwise get bored.
5. Ask your team to push back on your ideas
If you try to sell them on the idea, they may nod in the room and do nothing afterward. Asking for objections tests the idea + gets everyone aligned before you commit to it.
6. Start by building the part you understand the least
If you leave the confusing part until the end you might find out it doesn’t fit and have to rebuild everything around it.
7. End every email with an action needed
Name the person responsible, the action they need to take, and the deadline. Joe says this rule increased productivity in his business by 35 to 40%.
Thanks for coming on @FU_joehudson and sharing how you run your business.
Search “BigDeal pod” on youtube.
I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.
A deep analysis of what may have lead to the Nepal glacial collapse and a breakdown of how the flood overtook communities in a matter if minutes. #Nepal#flood#weather
Still the best hour on graph engineering ever recorded, Andrew Ng breaking down how to build agentic knowledge graphs from scratch:
00:00 - what agentic knowledge graphs actually are
03:05 - building a graph from scratch
13:58 - the architecture behind multi-agent systems
22:57 - building a real one with Google ADK
01:06:02 - why graphs are the future of AI agents
I've seen $500 courses that teach less.
Watch it, then take it further with my step-by-step guide on graph engineering below.
An Anthropic engineer shared the exact system they use as a second brain.
Three folders. One file. One evening to build.
Most people use Claude the same way every day. Open a new tab. Rebuild context. Get an answer. Close the tab. Tomorrow it remembers nothing. You are still the one holding all the context. You are still the one resetting.
This architecture solves that problem.
The system is built around three folders and one file.
raw/ holds everything unstructured. Articles, transcripts, PDFs, voice memos, screenshots. Drop it in and never touch it again. Immutable ground truth.
wiki/ is where Claude converts everything in raw into structured, linked, cross-referenced knowledge. Clean. Organized. This is the folder Claude actually thinks from. The human reads it. The model writes it.
output/ is where finished work lands. Reports, posts, documents, presentations. Everything Claude builds using the wiki as its source.
At the center is CLAUDE.md. Not a prompt, but a persistent layer of identity, preferences, goals, and project context. Claude reads it before every session. You never explain yourself again.
Five automations run the system.
Ingest captures and extracts new sources into the wiki. Write retrieves context and drafts outputs. Manage links decisions to context. Review summarizes and updates. Maintain prunes and improves connections.
Every session adds to the system. Every source makes the wiki smarter. The returns compound over time.
One month in, context stops disappearing. Three months in, the vault surfaces ideas you forgot you had. Six months in, the gap between compounding and resetting becomes impossible to ignore.
Build once. Maintain daily. Let it compound.
Bookmark this.