A full-spectrum behavioral, psychological, and professional analysis of the Aiyarise team's weekly Level 10 — what the team does, what the team is becoming, and what the structural gap looks like between the two.
Over seven weeks the Aiyarise Level 10 has performed a single, repeated experiment: can a five-to-six person consultancy with an evangelical founder, a Harvard-MBA strategist, a methodical systems architect, an absent-then-present advisor, a quiet builder, and a learning-mode admin run a structured weekly that produces decisions instead of monologues?
The answer is: partially, with a clear and worsening structural drift, increasingly compensated for by Sandy Liu's strategic discipline, Greg Shortreed's surgical agenda interventions, and a slowly-emerging in-meeting culture of honesty.
Brayden generates more strategic surface area than the team can metabolize in 90 minutes per week. Sandy is the only person consistently containing the surface area. Greg is the only person consistently auditing the agenda. Cameron, when present, is the only person consistently delivering plain-language reframes. Jeremy and Victoria are competent and under-asked.
Brayden Everton speaks 40–60% of every meeting. Runs the agenda, derails the agenda, and apologizes for derailing the agenda — often in the same five minutes. Simultaneously the team's largest accelerator and its largest source of meeting-time loss.
Sandy Liu must repeat her strategic correction 2–3 times per meeting to be heard. When she lands, she lands; when she doesn't, the team makes a worse decision. Every major framing decision in the seven-week window came from her.
Scorecards skipped in every meeting — no metrics exist to review. IDS has been hacked-in-flight or tabled in all but one. Rocks devour 30–45 minutes meant for status; real client decisions get crammed in around them.
The team's willingness to speak frankly about itself has grown linearly. Meetings 4/1–4/15 were polite; 4/22 onward introduces direct process challenges. By 5/13 Cameron is publicly disclosing about ego and peership ("I never thought I'd work for you, but I honestly don't care"). Victoria reads aloud private texts from Brayden to amplify the team's culture norms.
You want to move fast, do it yourself; you want to do a good job and travel far, do it together. — Greg Shortreed, 2026-05-06
A coded challenge to Brayden's lone-wolf workstyle that would not have surfaced in week one.
Brayden's all-nighter pattern is normalized. It is mentioned in five of seven meetings, often twice. The team laughs but does not push. The same pattern produces real artifacts (the kernel/proposal-generator, brand voice v2, Kasian charter) — and produces the unilateral scope creep that Sandy then has to walk back. It is the engine and the leak at once.
Greg's two gentle care-flags ("Brayden, not just Tuesday, man" on 4/1; "you doing an all-nighter to get something done is good to get us started — but…" on 5/6) are not enough.
Brayden is the company's largest single asset and its largest single operational risk. The risk is not that he will under-deliver — he over-delivers — but that the over-delivery creates a structural dependency the team cannot scale beyond, and a meeting rhythm the team cannot stabilize while he remains the only facilitator.
Formalize Sandy's co-facilitation authority on the L10. Convert what is already happening informally into procedural authority. This compresses ~30% of weekly meeting drift in a single move — without changing anyone's actual behavior, just by giving her a procedural lever to act on the patterns she already sees.
Brayden's all-nighter pattern, combined with his structural dependency on the team. The company cannot afford for him to burn out. Greg's two gentle flags are not enough. The team needs an explicit peer-care norm — any time he discloses an all-nighter, the chair responds with one of three structured prompts: what's the artifact, what would have allowed this to wait, what does the team take off your plate this week.
What does Jeremy's scope look like post-Shea? Jeremy is now the sole AI Systems Developer. Greg has flagged his own May 29 deliverable as at-risk due to family pressure. Technical-delivery capacity has materially contracted. Not discussed in the 5/13 meeting. Should not be deferred another week.
Greg's contract-evaluation tool (4/15). Built. Productizable. Not yet productized. Brayden's instinctive scope-creep — "apply it to specifications and drawings… tender document review for risk analysis" — suggests Greg has built something the company is not yet ready to commercialize. Spend 30 minutes scoping: paid offering, lead-magnet, or discontinued experiment.
Risks are surfaced, agreed verbally, then dissolved without an owner or date. Kasian contract (open since 4/8). Agent safety (open since 5/6). Fear-based-branding workshop (open since 4/29). Security expertise gap (open since 5/6). The fix is a hard rule: no IDS issue closes without owner + ISO-format date.
Click into any team member to open a slide-out drawer with their full psychological, professional, and behavioral profile.
02 / ProgressionEach meeting as an accordion — what happened, what shifted, what stayed broken across all seven weeks.
03 / PatternsThe two-body problem, the three quieter voices, structural friction, decision-quality patterns, the unaddressed facts.
04 / ImprovementsStructural, behavioral, sustainability, hygiene, strategic. Filter by tier; each opens to a concrete intervention.
05 / QuotesFilterable archive of every verbatim quote that captures a voice, a moment, or a turning point across the seven meetings.
The team is in a substantially better operating state at 5/13 than at 4/1. The trajectory is positive. The structural discipline is the gap between good and durable. Close it now, before the team grows beyond six people and the founder's centrifugal energy becomes harder to contain.