All Notes

Resume
2026 · profile
Feyi Agbaje Resume
About Feyi Agbaje
2026 · profile
Systems Design Engineer & IESE MBA. 9+ years across enterprise software, AI research, and operations.
Versa
2026 · flagship
Versa is a live daily word game from Dear Barry Games. I built the content quality system for generation, model evaluation, human review, curation, and product analytics.
Inside the Frontier
2025-26 · flagship
I turned a primary-source AI corpus into a grounded Atlas for comparing how frontier labs train, evaluate, and govern model releases without separating the claim from the evidence.
Daybreak
2026 · flagship
I took a GLP-1 companion from a weak generic tracker to a focused product thesis, then carried the strategy through product requirements, privacy boundaries, interaction design, and a deployed build.
Design Studio
2026 · flagship
I built a design-system studio to stop AI coding agents from inventing a new visual language every time they touch a product. It turns visual decisions into reusable tokens, semantic roles, and agent-readable constraints.
Maya Codex
2022 · enterprise
I led a joint research program asking where language models could genuinely help 3D artists learn Maya, where they would fail, and how those failures should change product strategy.
Bifrost Platform Foundations
2018–21 · enterprise
I helped turn an emerging procedural graph system into a product people could find, navigate, reuse, and adopt without breaking established Maya workflows.
Research Operations
2021–23 · enterprise
I turned a research bottleneck into reusable infrastructure: faster recruitment, a shared knowledge system, guarded self-service, analytics, and operational automation for a complex enterprise product organization.
Cached Playback
2018–19 · enterprise
I redesigned a technical caching feature around the way animators actually work, improving discoverability, learnability, control, and recovery while reducing a costly review loop.
Email Feyi 2022

Maya Codex

I led a joint research program asking where language models could genuinely help 3D artists learn Maya, where they would fail, and how those failures should change product strategy.
enterpriseAI-assisted creative workflows
Role
User Research + Research Operations lead
Autodesk side of a joint Autodesk × Microsoft program
Focus
AI-assisted creative workflows
Trust · failure recovery · learning · opportunity definition
Skills
AI product research · Product strategy
Diary studies · co-design · synthesis · executive communication
Tools
Maya · Codex-powered plugin
Interviews · diary studies · co-design workshops
00 / Question

“Add AI” was not a useful product strategy.

Autodesk and Microsoft wanted to understand where natural-language AI could genuinely help people learn Maya, and where early language-model behavior would break trust.

I led the Autodesk-side program across interviews, diary studies, co-design, synthesis, and strategy. The work focused on real task attempts, not opinions about hypothetical AI.

14
individual interviews
5
diary studies with the Codex-powered plugin
20+
co-generated concepts
01 / Program

Two research rounds, then an explicit strategy phase.

Round one aligned stakeholders and mapped where the learning journey broke across advanced users, novices, and an educator. Round two narrowed to novice behavior and added diary studies over multiple days.

The strategy phase synthesized the evidence, ran opportunity and co-design workshops, reduced more than 20 concepts into five opportunity areas, and recommended one direction.

01
Discover
Interviews across expertise levels and teaching roles.
02
Observe
Diary studies capture behavior after repeated AI failure.
03
Co-design
Pressure-test concepts with people who use and teach Maya.
04
Recommend
Turn findings into opportunity areas and product direction.
02 / Failure modes

Trust was shaped by what happened when the model was wrong.

The most valuable moments were not successful commands. They were the points where the AI misunderstood the user and the user had to decide whether to rephrase, retreat to familiar menus, or stop asking.

That led to a durable design principle: failure should be legible. An assistant that fails opaquely trains users to stop using it; one that explains limits and offers a reliable next step can keep the user in the learning loop.

AI product principle
In professional tools, the failure experience can determine trust more strongly than the success experience.
03 / Strategy

Distinguish between guidance and execution.

The research compared assistance postures: recommending trusted learning material, guiding a user step by step, or executing commands directly. Those modes earn trust differently depending on expertise and task risk.

The final work defined personas, opportunity areas, and a recommended direction that leadership at Autodesk and Microsoft could use beyond the study.

04 / Impact

Research became product direction.

The program produced five opportunity areas from more than 20 concepts and one recommended direction. The findings informed Autodesk AI strategy and Microsoft’s understanding of LLM behavior with non-programmer users.

Autodesk publicly announced Maya Assist with Microsoft the following year. This case does not claim a direct one-to-one feature lineage; the evidence is that the program defined product questions, users, failure modes, and opportunity space before generative AI assistants became mainstream.

5
opportunity areas defined
1
recommended direction
17 weeks
from research framing to strategy
Research strategy
17-week program with interviews, diary studies, and co-design.
AI product judgment
Focused on failure recovery, trust, and assistance posture.
Cross-company alignment
Translated evidence into recommendations for Autodesk and Microsoft.
Forward relevance
The same guide-vs-do and copilot-vs-agent questions remain central to AI products.

Working on a hard product problem?

I’m exploring GTM Strategy, AI Product, Product Strategy, and Forward Deployed roles.