Tools we wish we'd had, made simple.
Not a course. Not another platform to log into. A set of templates and habits that worked β take what's useful, adapt it, run with it yourselves.
Toolkit
These are templates, not a service. Copy them into whatever you already use β Notion, Google Docs, a notebook. The point isn't the tool, it's the habit.
Subject Playbook Card
One card per subject/module. Forces you to distill instead of re-reading slides the night before.
- The 1 idea that mattered most
- Where it applies in your actual job
- 1 question you'd still ask the professor
Next-Move Steps
A short, honest sequence β not a 5-year plan, just the next few real steps.
- Name the actual decision, not the vague feeling
- List who already made a similar move β ask them, don't guess
- Pick one thing to test before committing
Before / During / After Checklist
Same shape every time, so starting isn't the hard part.
- Before: what decision does this research inform?
- During: log sources as you go, not after
- After: one paragraph, not a folder of PDFs nobody rereads
Grounded, not hustle-culture
Three habits that hold up under a real executive schedule (family, travel, a job that doesn't pause for class):
- Time-block the thinking, not just the meetings β a calendar full of calls with no space to actually decide anything is the most common trap.
- Weekly review, 15 minutes β what moved, what didn't, what's the one thing next week.
- Single-task the hard stuff β multitasking on the easy parts is fine; the one thing that requires real thinking gets its own block, phone away.
How we work now
A lot of good work still lives in shared folders β "final_v3_FINAL.docx", emailed back and forth, no history of who changed what. There's a better default now, and you don't need to become an engineer to use it.
Slides became documents you build together
This toolkit itself was never a slide deck β it's a page, built collaboratively, iterated in place. That's not a style choice, it's becoming the default way real work gets shipped: something everyone can open, edit, and see change, instead of a static file someone emails around.
GitHub, not another shared folder
A shared folder only knows the latest version. GitHub keeps every version, who changed it, and why β so nothing gets silently overwritten. You don't need to learn it by hand: that's what your AI coworker is for.
The thought, and what actually works
The science of managing a brutal workload isn't new or mysterious β it's well studied. The gap is usually exposure, not effort: most people default to sticky notes and a notes app because nobody showed them the smarter version. Here it is.
"I have so much to read, I can't keep up."
Stop tracking it in your head or a pile of tabs. Put every reading/task into three columns β To Do, Doing, Done β a Kanban board. Cap how many things can sit in "Doing" at once (2-3, not 15). Seeing the pile shrink left-to-right does more for your head than any planning app.
"My notes are scattered across three apps and a notebook."
Pick one place. Since you're already keeping work in a tracked GitHub folder (see How We Work Now), your planner can live right there as a real project β each task an item, the board a live Kanban view, always current because it's the same place your AI coworker already works.
"I walk out of calls and can't remember what we agreed to."
Manual note-taking during a live conversation is a bad use of your attention β you're either present or transcribing, rarely both. Tools like Granola listen in the background and hand you organized notes and action items the moment the call ends, so you can actually be in the meeting.
"Everything feels equally urgent."
It isn't β that feeling is what an unranked list produces. Go back to the one ranked list from the Method below. If you can't rank two things against each other, that's the actual signal you need more information, not more hours.
A method for an accelerated year
An MBA compressed into months, on top of a full-time job, doesn't leave room for winging it. Software teams solved a similar problem β too much to do, too little time, everyone pulled in different directions β with something called Scrum. Strip out the jargon and it's four habits.
Keep one running, ranked list
Everything you might do β readings, applications, networking asks β in one place, ordered by what actually matters this week. Not everything on it gets done. That's the point: it makes the trade-off visible instead of pretending you'll get to all of it.
Work in 1-2 week blocks
Pick a small, real set of things for the next block, not the whole semester. At the end, look at what actually got done β not what you planned β and adjust the next block. Short cycles catch problems while they're still small.
A 2-minute check, not a meeting
What did I finish, what's next, what's stuck? Three lines, daily or every other day, to yourself or a study group. It's not a report to a boss (see Working Together) β it's a habit that catches drift before it becomes a crisis.
A short retro, every block
What worked, what didn't, what's one thing to change next block. Two minutes. Skipping this is how the same avoidable problem repeats all year.
β One ranked list, updated weekly Β· β A block length picked (1-2 weeks) and stuck to Β· β A 2-minute check every few days Β· β A retro at the end of each block Β· β One thing changed based on the retro, not zero
Things that will probably happen to you
These aren't generic MBA-life tips. They're patterns measured from one actual cohort's year (see the Almanac for the full findings) β offered as "here's what happened once," not "this always happens."
"The group chat's gone quiet β did I miss something?"
Probably not. In IBEAR 40, message traffic dropped about 47% from August's peak to January, tracking recruiting season, not disengagement. If it feels quiet mid-year, that's the calendar, not a sign something's wrong.
"Everyone else seems to be talking more than me β am I not fitting in?"
In one cohort, five people produced about a third of all messages. Most people aren't big talkers, and 87% of people who did post got a reply. Volume isn't belonging.
"Some classmates barely post β are they checked out?"
Regional communication styles measurably differ β some groups start more conversations, others reply more and start fewer. Read quietness as a style difference before reading it as disengagement.
"Will I remember the coursework or the people?"
In the exit survey, the top five "extremely satisfied" factors were all community and environment β facilities, collegiality, shared trips β not a single academic factor made the top five. Invest in the shared experiences on purpose; they're not the side dish.
"When does the recruiting crunch actually hit?"
In one cohort, the career-focused share of conversation jumped from 0% to over 20% in the final weeks. If you can see it coming on the calendar, you can prepare before it, not during it.
"Is it worth saying thank-you publicly, or is that performative?"
It was the most widely shared behavior measured β 94% of regulars posted some form of thanks. Cheap, real, and near-universal. Do it; you're not the only one who'll feel it's a little much.
The network is already there for you
No directory of names published here β that's on purpose. The network exists; how you use it is between classmates, not a public list.
Alumni in the atlas
IBEAR 1β40, 64 countries. 86% work in their country of citizenship β the network's weight sits in Pacific Rim capitals, not around LA.
Messages mined, one cohort
IBEAR 40's WhatsApp corpus β community factors topped exit-survey satisfaction, above anything academic.
The full IBEAR Almanac β course dynamics from IBEAR 40's year, plus an interactive atlas of where alumni work (filter by industry, era, country). Compiled by IBEAR 40 for the classes that follow.
What's actually within reach
Being at USC, in Los Angeles, in California, puts real doors closer than most people realize β most classmates just never hear about them unless someone points. Four that are worth knowing about.
The Lloyd Greif Center
USC's own entrepreneurship engine β the oldest program of its kind in the US. The Greif Incubator gives promising founders office space, mentoring, and legal/business support from MVP to fundraising, and the Marshall Venture Fund puts capital behind ventures with USC alumni, faculty, or staff on the founding team. This is alumni-eligible, not just current-student-eligible β worth checking even years after graduating.
The O-1 path, if you're building something
For founders with real traction (funding, press, notable achievement), the O-1A category has no annual cap and no lottery β unlike H-1B, timing isn't a gamble. It's not automatic and it's not legal advice β talk to an immigration attorney early, not after you need it β but it's a real, commonly used path for accomplished international founders building in the US.
Forming a company here is more mundane than it sounds
An LLC in California runs roughly $70 to file, $20 for the follow-up filing, and $800/year from year two on β the first year is currently fee-waived if you form in 2026. And as of this year, U.S. LLCs no longer have to file the federal beneficial-ownership (BOI) report that used to add paperwork on top. It's a Tuesday-afternoon task, not a legal saga.
The treks were rated best for a reason
In the exit survey, the Silicon Valley and Seattle treks were the two best-rated career-services experiences β not classroom sessions. If your cohort runs something similar, that's the highest-leverage, lowest-effort way to get in front of the ecosystem in person. Show up for those specifically.
Nobody wants to be the boss β and that's fine
Every IBEAR class has the same issue: a room full of people who already run things, none of whom came here to be managed by a classmate. That's not a bug to fix with a hierarchy β it's the actual shape of the group. These four habits work with that, not against it.
-
Rotate the lead A different person runs point each cycle β nobody is "the boss" for more than a few weeks at a time. Rotation removes the awkwardness of asking a peer to lead permanently.
-
Write the cadence down A shared doc that says "we sync every other Tuesday, 20 minutes" beats anyone having to personally chase people. The schedule does the asking, not a person.
-
Announce, don't assign Post what needs doing and let people opt in, instead of one person handing out tasks. People follow through more on what they picked than what they were told.
-
Small commitments beat big mandates One clear, small thing per person is more likely to actually happen than one leader trying to assign everyone's workload.
Two templates to copy
What: [the thing]
Why it matters: [one line]
If you're in: [how to opt in β reply, react, sign up]
By when: [date]
How often: [e.g. every 2 weeks]
Who's up: [rotating name]
Length: [e.g. 20 min, hard stop]
The one ask: [single thing to bring]