Handbook: pause First Impressions, create BYOD working group, reshuffle Power to the PC

[lukeheath]

Draft PR. Starting point for the working-group restructure conversation. Not ready to merge until we align on the questions below.

Proposed changes next release cycle (in this PR)

• First Impressions: paused. Engineering capacity redirects to Power to the PC.
• Power to the PC: Scott Gress joins as SWE (Konstantin moves out).
• BYOD (new working group): Konstantin Sykulev (Tech Lead), Andrew Mellor (SWE). Andrew moves over from MDM. Goal, PD, and QA TBD.
• MDM: Andrew Mellor removed. Backfill via open MDM SWE req.

End-state we're working toward

After we backfill and onboard the open SWE roles, each product group transitions to a working group. Eight working groups total.

#	Working group	Goal	Notes
1	First Impressions	Improve first impressions at workshops, conferences, demos.	Resumes after MDM backfill.
2	Power to the PC	Empower Windows users to fully leverage Fleet as an MDM.
3	BYOD	TBD. Starting point: BYOD device management, initial focus Android.
4	Apple @ Work (was MDM)	Increase and exceed maturity in Apple device management.
5	TBD (was Software)	Patch in hours, not weeks.	"Continuous patching" has a sisyphean quality. Mike floated "Last mile" or "Last mile patching." More than just patching: the goal includes the org-change / last-mile work (maintenance windows, calendar, notifications, etc.).
6	TBD (was Security & Compliance)	TBD.	Luke: define the goal first, then name it. What is the goal of "Security & Compliance"?
7	TBD (was Orchestration)	TBD. "Identity"?	What's the goal? Should drive a business outcome we'd put on an ROI slide at QBR.
8	DEX	Improve Digital Employee Experience using Fleet.

Open questions for Mike (and anyone else jamming)

1. Group 5 (was Software). Is "Last mile" / "Last mile patching" the right name? Is the goal "patch in hours, not weeks"?
2. Group 6 (was Security & Compliance). What is the actual goal?
3. Group 7 (was Orchestration). Is identity the right direction? What's the goal that drives Fleet revenue (or is QBR-worthy)?
4. Group 8. DEX vs. EDR vs. something else. Goal first, name second.
5. BYOD goal. Is it "manage employee-owned devices across Android and iOS" or narrower (Android-first)? Affects how we scope the team.

[mikermcneil]

@lukeheath 8 != EDR. Instead: I think? DEX + snow/ticket + ITAM +/- integration depth. Needs snappy name and goal — @allenhouchins noodling

Each group needs well defined customer ROI-based or Fleet business goal. Eg power to the pc’s goal is to increase the number of windows hosts enrolled in fleet, first impressions’ goal is to increase win rate, BYOD’s goal is to increase customers’ BYOD enrollment rates, apple@work’s goal is to increase the number of Apple devices enrolled in Fleet, auto-patching team’s goal is to decrease customers’ time to patch critical vulnerabilities - even in the face of (/ overcoming) last mile factors like handoffs, end user UX considerations, notifications, restarts, etc