PA offer to Sylvie and planning split
PA offer to Sylvie and planning split
Draft. Fae still needs to review this. Do not take anything here as certain or agreed.
Draft SCQH from Fae's conversation with Claude on 19 Oct 2026. Facts are what Fae described or what the linked sources say. Items marked (guess) are Claude's inference and need checking. Nothing here is agreed with Sylvie or Rufus yet.
SCQH
- Situation: Fae works three days a week across Sylvie's PA work and planning and coordination. In practice Fae runs weekly one-to-one check-ins with Sylvie, where Sylvie raises ideas, reminders and tasks. Fae captures backlog ideas and notes, chases Sylvie on reminders, and does admin and media-house or content-pipeline tasks for her, such as editing art reports. Fae also reads Sylvie's email in parallel and sometimes drafts replies or chases people. Other PA work includes children's US visa and British passport applications, and possibly setting Sylvie up in Taiwan. Sylvie is a co-founder. She has a list of art projects she wants to take on, not yet prioritised.
- Complication: When Sylvie asks Fae directly for something, and Fae raises it at stand-up, Rufus sometimes calls it not a priority. Uriel usually says "just do it", since he is not asked to do anything in return. Fae then gets mixed messages, even though Fae has time set aside for Sylvie's tasks. Priority confusion causes stress for Rufus, Sylvie and Fae. The AI tools do not yet show Fae's week in a way that separates Sylvie's requests, media-house work and Rufus's planning. Fae does not yet run the PA side smoothly enough to split time cleanly. Email is slipping behind other work because Fae does not yet have the context to triage it quickly, and Sylvie has little time to give that context. Fae does not do anything for Sylvie's meetings or preparation documents. Sylvie struggles with the volume of contact and wants a regular session to decide what and who to prioritise. Sylvie thinks that is outside PA work. Rufus, Sylvie and Fae agree it would be good, and that Fae would enjoy it.
- Question: How can Fae bring more flow to Sylvie as a PA, so that within two months the PA offer runs as a smooth operating rhythm and about half of Fae's time is clearly available for planning and coordination?
- Hypothesis: Not yet. Fae chose to clarify the situation, complication and question first.
Constraints (as Fae stated them): three days a week in total. The aim, in principle agreed by Sylvie and Rufus, is 1.5 days of PA work and 1.5 days of planning and coordination.
Issue tree
Unanswered questions stay unanswered. Add ✅ Answer. on the same line when one is settled.
- How can Fae bring more flow to Sylvie as a PA within two months?
- What does Sylvie want from a PA, and which parts does she want to hand over?
- How should Sylvie's requests reach the team and get prioritised, so that Fae does not get mixed messages?
- Who decides when Sylvie asks Fae directly and Rufus disagrees? Does Fae's time for Sylvie count as a planning decision?
- Where are Sylvie's requests recorded: Beads, a Sylvie list, or somewhere else?
- How does Fae get the context to run Sylvie's email fully?
- Is the weekend check-in the right way to build that context, and how long does it take?
- Which projects and contacts does Fae need to learn first?
- Does Sylvie want support with her meetings and with preparation documents?
- Does Sylvie want a regular prioritisation session with Fae, and what does it cover (projects, people, or both)?
- Which of Sylvie's art projects, if any, should Fae help with now?
- How does the PA side of Fae's week connect to the team weekly plan and the LTP project-management work?
- What is the right split of 1.5 days and 1.5 days, and how will it be reviewed?
Plan of work
Provisional. Dates and estimates are guesses to agree at the first check-in.
| # | Action | Estimate | Target date | Needs approval from |
|---|---|---|---|---|
| 1 | Agree the priority rule for requests that come directly from Sylvie (who decides, and what happens at stand-up) | 30 min | Before next stand-up | Sylvie, Rufus |
| 2 | Start a weekend email check-in with Sylvie to build context on her style, projects and contacts | 30–60 min a week, ongoing | Start the weekend of 24–25 Oct (guess) | Sylvie |
| 3 | Ask Sylvie what she wants from meetings support, preparation documents and a prioritisation session | 15 min | Next check-in | Sylvie |
| 4 | Decide where requests from Sylvie are recorded and how they show up in Fae's week | Half a day | Before the 1.5 / 1.5 split is tested | Rufus |
| 5 | Once context builds, draft an email triage skill for Sylvie's inbox | 1–2 days | After four weekly check-ins (guess) | Sylvie |
| 6 | Test the 1.5 / 1.5 split for four weeks and review | 4 weeks | Review at week four (guess) | Sylvie, Rufus |
Check-in points
- Sylvie and Rufus, together: the priority rule for direct requests, the 1.5 / 1.5 split, and whether a prioritisation session is in scope for Fae.
- Uriel: whether the recording and routing approach is simple enough for him to use day to day.
- Rufus: the recording system for requests from Sylvie, since it affects the team weekly plan.
Where actions are logged
Not yet. Once the plan is agreed, create Beads tasks linked to this file (see Beads conventions). Keep this file for the reasoning and questions, not the live task queue.
Sources
- Fae's description of the role and complications, shared with Claude on 19 Oct 2026 (this conversation).
- Sylvie person record.
- Briefing for Sylvie, 5 Oct 2026: the topics Sylvie wants a one-to-one on, and keeping her informed before team calls.
- Project management infrastructure, Level 2 SCQ: notes that Sylvie tasks people directly (Rufus, 9 Oct 2026), and that Sylvie's direct requests are prioritised like team work (Rufus, 9 Oct 2026, answered).
- Planning practice briefing, 21 Sep 2026: the SCQ method this draft follows.
