FICTIONAL SCENARIO · invented people and numbers · nothing here is saved

Two projects need the same specialist.

A manager at a fictional 40-person company has one senior data engineer and two projects that both need her. Explore the options and decide what to do.

Work requirement

Project Atlas: data platform migration

Data engineering · 24 h/week for 8 weeks

Hard deadline: contract renewal

Work requirement

Project Beacon: customer analytics dashboard

Data engineering · 16 h/week for 6 weeks

Soft deadline: quarterly review

Available capacity

Maya: about 30 h/week

Needed: about 40 h/week

Gap: about 10 h/week of data engineering

Compare the options

Trade-offs: Daniel + AI assistant for repetitive dashboard work

For

Covers the repetitive 60%
Low cost, easy to reverse

Against

AI output needs checking
Doesn't help with Atlas

Supporting evidence

Maya, the only senior data engineer, has about 30 focused hours per week.
Capacity plan (fictional) · FACT
Daniel (analyst) rates 3/5 on SQL and has built two dashboards before.
Skills profile (fictional) · FACT
Beacon's dashboard work is roughly 60% repetitive query and chart setup.
Team estimate (fictional) · FACT
Staffing both projects with Maya needs ~40 h/week, so one project will slip without a change.
Enpowerly inference · INFERENCE

Suggested next step

Keep Maya on Atlas. Give Beacon to Daniel with an AI assistant.

Reasoning: Atlas has the hard deadline and needs Maya's expertise. Most of Beacon is repetitive work that Daniel can handle with AI help, while Maya reviews for 3 hours a week. Hiring is unlikely to start in time.

Assumptions

The 60% repetitive estimate is roughly right
Daniel can spend 16 h/week on Beacon
Customer data can be used with the AI tool under company policy

Missing information

How Daniel's other work will be covered.

Next step: run it for 2 weeks and check Beacon's progress and Maya's review hours.

Your review

Nothing happens automatically. You decide. In this demo your choice isn't saved.