**TL;DR** — The team approved the Q3 pricing test and pushed the mobile redesign to August. Two action items are unassigned.
**Decisions made**
- Run the pricing A/B test on the Pro plan starting July 1.
- Delay the mobile redesign to August to avoid the holiday code freeze.
**Action items**
| Task | Owner | Due date |
|---|---|---|
| Set up pricing test in billing | Priya | Jun 27 |
| Draft August launch timeline | unassigned | unassigned |
| Tell support about the price change | Marco | Jun 30 |
**Open questions**
- Who signs off on the final August date?
ヒント「所有者または日付を発明しない」ルールはこれを信頼できるようにします。 AI はそうでなければ尤もらしい-しかし間違った名前でギャップを埋めます。 Zoom/Meet トランスクリプトを最良の結果のために直接貼り付けます。
Technical
1. "Walk me through how you've structured a sourcing funnel for a role with under 200 qualified candidates in the market." → Strong answer: a specific example with search strategy, outreach rate, and how they adapted.
Behavioral
2. "Tell me about a time a hiring manager wanted a candidate you thought was wrong for the role. What did you do?" → Strong answer: held a position with data, didn't just defer.
Thinking questions
3. "This role has a two-week time-to-fill target. What breaks first and how do you manage it?" → Strong answer: surfaces pipeline risk, sets expectations early, doesn't promise what they can't control.
LinkedIn (professional, ~150 words): "Most agencies blame scope creep for missed deadlines. The data says it's usually something quieter: nobody agreed on what 'done' looks like at kickoff. We analyzed 200 completed agency projects and found that the ones finishing on time shared one habit... [link]"
Twitter/X (~240 chars): "Agencies that finish projects on time don't have better clients. They agree on 'done' before work starts. 3 questions we ask every kickoff: [link] 🧵"
Instagram (caption, visual hook): "The one question that prevents scope creep 👇 (swipe to see all 3) Most agencies never ask it at kickoff. Full breakdown at the link in bio."
Facebook (~80 words conversational): "We looked at 200 agency projects to find what on-time delivery actually had in common. It wasn't better tools or bigger teams. It was one kickoff habit. Worth a read if your deadlines slip more than you'd like. [link]"
Threads (casual, 2 short paras): "Hot take: scope creep is a kickoff problem, not a client problem. Read our breakdown — link in bio."
Q1: What two crops did the Dust Bowl destroy most severely in Oklahoma between 1934 and 1936?
Type: Recall
Sample answer: Wheat and cotton were the two crops most severely destroyed during the Dust Bowl years described in the passage.
Q2: Why did many families leave even when they owned their land outright?
Type: Inference
Sample answer: Even landowners left because dust storms made farming impossible for years at a stretch, meaning owning the land didn't protect them from losing their income and food supply.
Q3: The author argues that the Dust Bowl was partly caused by farming practices. Do you think knowing that changes how we should respond to today's droughts? Explain using the text.
Type: Synthesis
Sample answer: Varies — accept any response that connects the passage's evidence about over-plowing to a current policy or personal action.
Subject: re: cutting your support ramp time
Hi [Name],
One more reason this might be worth a look: [Similar company] had the same "new reps drowning for weeks" problem and got first-week resolution rates up 22% after switching.
If ramp time isn't a priority right now, no worries — just reply "not now" and I'll close the loop.
Otherwise, open to 15 minutes Thursday?
[Your name]
**This week**
- Shipped the onboarding email sequence; open rate at 41% vs. 29% baseline.
- Closed two enterprise pilots — Meridian Health and Solis Finance (combined ARR: $84,000).
- Reduced P1 ticket backlog from 34 to 11 by reallocating two engineers from the feature queue.
- Completed Q3 headcount plan; submitted to HR on Thursday.
**Next week**
- Priya: finalize security review for Meridian (due Thu).
- Tom: start sprint 14 with new backlog priority order.
- Me: present Q3 plan to leadership on Wednesday.
**Blockers**
- Need sign-off on the contractor extension for Tom's team by Monday — delays sprint 14 otherwise.
ヒント貼り付ける前に「配信されたオンボーディングメール」ではなく、ノートに数字を書くこと。 「オープンレート 41% vs. 29% ベースライン」はリーダーシップが覚えるものです。 AI はあなたが与えなかった指標を発明することはできません。
A support team told me their new hires were "useless for a month." Their words, not mine.
The problem wasn't the people. New reps were hunting through 400 pages of docs that changed every week — so they guessed, or pinged a senior rep, who then stopped doing their own job.
We gave them one answer layer trained on those same docs. First-week resolution rates went from 51% to 73%.
The lesson: onboarding speed is usually a findability problem, not a training problem.
Curious how other support leaders are tackling ramp time — what's worked for you?
**Decision: Hire vs. Contract for Design Role**
To: [Director] | Date: Jun 17
**Context**
The onboarding project needs a designer by July 1 to hit the Aug 31 ship date. The role has been open for six weeks; the pipeline has two candidates but no offer-ready finalist.
**Options**
| Option | Pros | Cons | Cost |
|---|---|---|---|
| Extend contractor (Lena) | Available now, knows the product | 20% premium, not a long-term fix | $12,000 for 8 weeks |
| Wait for hire | Right long-term | Delays project 3–6 weeks | $0 now, risk of Q3 miss |
| Freelancer via agency | Fast, low overhead | Ramp time, no product context | $8,000–$14,000 |
**Recommendation**
Extend Lena's contract through August. She's already ramped, and missing the August date costs more than the premium.
**What we need from you**
Approval to extend Lena at the current rate through Aug 31. I need this by Monday to give her enough notice.
ヒントあなたの推奨を明示的に述べます。 「オプション B」は推奨ではありません。 「I は X を推奨します、Y のため」を言うことはあなたを強制します。決定メーカーが迅速に移動するために必要なものは正確です。 すべてをヘッジするメモは行動を取得しないメモです。
Overall fit: Possible — strong on the technical side, light on the team leadership the spec asks for.
Matches:
- 6 years in data engineering, all in fintech (spec asks 4+).
- Hands-on with dbt and Snowflake, which the spec names explicitly.
- Led a pipeline migration project end-to-end.
Gaps:
- No evidence of managing other engineers — spec requires leading a team of 3+.
- No mention of vendor negotiation or tooling budget ownership.
- ML pipeline experience listed but no specifics; could be shallow.
Question to ask: "The role manages two junior engineers from day one — have you had direct reports before, and what did that look like?"