Open to PM & Project Management roles

Fiyin
Alasoluyi(Miss Fifi)

Product & Project Manager specializing in Web3 and STEM environments. I've built a live product from scratch. Nexura on the Intuition ecosystem. I bring frameworks, systems thinking, and ship-it energy to every project.

See My Work ↓ Why Hire Me
8+
PM Frameworks mastered
1
Live demo product built
3
End-to-end simulations

A note on experience

I haven't worked inside a company yet, and I'm not hiding that. What I have done is build a real product (Nexura on the Intuition ecosystem), write production-quality PRDs, run sprint simulations, and apply every framework in this portfolio to actual decisions. Not just textbook exercises. I learn fast, I ship things, and I care about getting it right.

What I Know

Skills & Competencies

Each skill below includes what it is, when I'd use it, and where I applied it on Nexura. No textbook summaries. Real context.

Product Management
Product Vision & Strategy
Defining what a product is for, who it's for, and what success looks like. This comes before writing a single feature.
Use this first. Without a clear vision, every feature decision becomes a guess.
→ Applied: Nexura PRD. Vision section, builder-facing positioning
Product Management
Product Requirements Documents
Writing structured documents that align engineering, design, and stakeholders on what to build and why, before build begins.
Every time a feature is complex enough to have misunderstandings. PRDs prevent expensive rework.
→ Applied: Full Nexura PRD with vision, governance, Studio, Nexon
Product Management
Jobs-to-be-Done (JTBD)
Framing user needs as the "job" they're trying to accomplish. Not what they say they want, but the reason behind it.
When building user stories or defining who the product serves. Cuts through feature requests to real motivation.
→ Applied: Nexura builder personas. "When I discover an ecosystem, I want to earn while I explore"
Project Management
Agile / Scrum Methodology
Running work in short sprints with defined ceremonies: planning, standups, reviews, and retrospectives. Iterative and adaptable.
When requirements will evolve, the team is small-to-mid size, and fast feedback matters more than a perfect upfront plan.
→ Applied: PM Sprint Simulation. Full 2-week sprint cycle built end-to-end
Project Management
Risk Register & Management
Identifying risks before they become problems, rating by likelihood and impact, then assigning mitigations and owners.
At project kickoff and reviewed every sprint. Keeps the team ahead of problems instead of reacting to them.
→ Applied: Nexura risk register. Smart contract failure, low builder adoption, governance attacks
Project Management
OKR Setting
Translating strategy into measurable goals. Objectives (directional) + Key Results (specific, measurable, time-bound).
Quarterly planning cycles. Aligns the team on what matters without micromanaging how they get there.
→ Applied: Nexura Q1 OKRs. Onboarding, engagement, ecosystem integrations
Web3 Domain
Tokenomics & Governance Design
Designing incentive systems using tokens. How tokens are earned, locked, and used to make decisions in a decentralized system.
Core to any Web3 product that needs sustainable user behaviour and community trust in decisions.
→ Applied: Nexura veTRUST governance + $TRUST token mechanics
Web3 Domain
Semantic Graph & Intuition Ecosystem
Building products on Intuition's Atoms + Triples data layer. Structured claims on-chain, composable knowledge graphs.
When the product needs trust, discoverability, and reputation signals that are verifiable and community-generated.
→ Applied: Nexura discovery engine built on Intuition's semantic graph
Execution
Stakeholder Communication
Planning who needs what information, how often, and in what format. Ensuring no one is surprised and trust stays high.
Always. Poor comms kills projects that have good plans. Especially critical across builders, investors, and protocol teams.
→ Applied: Nexura stakeholder map + builder-facing Studio workspace pitch

Soft Skills

The interpersonal foundation behind every framework, decision, and deliverable.

Communication Skills
Clearly conveying ideas to teams, stakeholders, and customers.
Writing clear product specs, reports, and updates.
Active listening to understand problems before proposing solutions.
Leadership & Influence
Guiding teams without necessarily having direct authority.
Motivating cross-functional teams to achieve goals.
Negotiating trade-offs between stakeholders, features, and timelines.
Collaboration & Teamwork
Working closely with engineers, designers, marketing, and sales.
Building trust and empathy with team members.
Encouraging open dialogue to solve conflicts constructively.
Problem-Solving & Critical Thinking
Breaking down complex problems into manageable pieces.
Identifying risks and anticipating challenges early.
Making decisions using data, user feedback, and intuition.
Adaptability & Flexibility
Adjusting plans when priorities shift or unexpected issues arise.
Being open to feedback and new ways of doing things.
Handling ambiguity without losing focus on goals.
Time & Priority Management
Balancing multiple tasks and deadlines efficiently.
Knowing what is urgent vs. important for the team or product.
Delegating effectively when necessary.
Empathy & Customer Focus
Understanding user needs deeply.
Advocating for customers in internal discussions.
Using empathy to improve products and processes.
Conflict Resolution
Managing disagreements between stakeholders or team members.
Finding compromises that satisfy different perspectives.
Maintaining team morale during challenging situations.
Negotiation Skills
Securing resources or buy-in for initiatives.
Balancing competing priorities across teams.
Navigating internal politics without causing friction.
Vision & Strategic Thinking
Seeing the big picture for product direction or project goals.
Anticipating market trends or project risks.
Aligning day-to-day actions with long-term objectives.
What I've Built

Demo Projects

Three end-to-end projects. Every document, decision, and artifact here was built by me. No templates, no shortcuts.

Web3 PRD Governance Tokenomics
01. Featured Project
Nexura
Discovery & Earning Platform
on the Intuition Ecosystem
NX

Nexura is a Web3 engagement engine that lets users discover the Intuition ecosystem and earn $TRUST rewards through meaningful interaction. I owned the full product definition, from vision through governance to builder-facing features.

Problem I solved

1
Intuition had powerful infrastructure but no clear user entry point for discovery
2
Builders lacked a workspace to launch reputation-gated campaigns
3
No sustainable reward loop to keep users returning and contributing quality signals

Deliverables I produced

Full PRD Product Vision veTRUST Governance Design $TRUST Tokenomics Studio Workspace Spec Nexon Progression System User Personas (JTBD) Feature Prioritization (RICE) Risk Register Q1 OKRs

Decisions Log. Key product calls I made

DecisionWhyTrade-off accepted
Vote-escrow ($veTRUST) over flat token governance
Aligns long-term holders with quality decisions; discourages mercenary voting
Reduced short-term participation from casual users
Builder Studio as a separate workspace (not embedded)
Different mental model for builders vs. explorers; mixing them confuses both
Higher dev cost; two surfaces to maintain
Nexon as progression layer, not just badges
Progression unlocks real utility (higher reward multipliers, governance weight)
More complex to balance; risk of gamification abuse
Agile Sprint Scrum
02. Simulation
PM Sprint
Simulation
SP

I ran a full 2-week Agile sprint as if I were PM at a real startup. Backlog grooming, sprint planning, daily standup format, and a written retrospective.

Sprint Backlog (Sample)

StoryPriorityPointsStatus
User can connect wallet and see Nexon levelHigh5✓ Done
Studio: create a new campaign with reward configHigh8✓ Done
Discovery feed: filter by Atom categoryMed3→ In Progress
$TRUST reward calculation & distribution logicHigh13✓ Done

Retrospective. What I documented

Went well: Clear definition of done reduced back-and-forth on wallet story. Reward calculation story was scoped tightly.
Improve: Discovery feed story was too broad. Should have been split into 3 smaller stories before sprint start.
Comms Stakeholders Planning
03. Exercise
Stakeholder
Management
ST

Mapped every stakeholder for Nexura: builders, protocol team, token holders, early users. Built a full communication plan showing what each group needs and when.

Stakeholder matrix (sample)

StakeholderInterestCommunication
Intuition Protocol Team
Technical alignment
Weekly async update + monthly sync
Builders (Studio users)
Platform utility + ROI
Launch notes + campaign analytics dashboard
$TRUST Token Holders
Governance + returns
Governance proposals + voting period alerts
How I Think

Frameworks I Use

Not memorized. Applied. Each framework shows how I'd use it on your project, and where I tested it on Nexura.

R
RICE Scoring
Reach · Impact · Confidence · Effort
Prioritizes features by calculating a score: (Reach × Impact × Confidence) ÷ Effort. Turns subjective debates into defensible decisions.
Skip when: you have <3 features to compare, or when all options have nearly equal scores. Use judgment then.
NEXURA APPLICATION
Scored Studio vs. Discovery Feed vs. Nexon Progression. Discovery Feed scored highest (largest reach, high confidence from comparable products). Nexon scored 2nd. High impact but lower confidence.
M
MoSCoW
Must · Should · Could · Won't
Categorizes features by necessity for a given release. Prevents scope creep by forcing clear "Won't for this version" decisions.
Skip when: all features genuinely must ship together or when the team is already aligned. MoSCoW meetings waste time on obvious things.
NEXURA APPLICATION
Must: wallet connect, Atom discovery, $TRUST rewards. Should: Studio campaigns. Could: Nexon leaderboard. Won't (v1): cross-chain bridging, DAO treasury.
J
Jobs-to-be-Done
JTBD Framework
Reframes user needs as "When I _____, I want to _____, so I can _____." Focuses on the outcome the user is trying to reach, not the feature they request.
Skip when: you're iterating on a known, stable feature. JTBD is most valuable during discovery and strategy phases.
NEXURA APPLICATION
Builder JTBD: "When I want to grow my protocol's user base, I want to launch targeted campaigns, so I can reward real engagement, not airdrop farming."
O
OKRs
Objectives & Key Results
Sets ambitious directional goals (Objectives) with 3–5 measurable outcomes (Key Results) that prove the objective is being reached. Time-boxed, usually quarterly.
Skip when: the team is in pure execution mode on a locked scope. OKRs add value during planning, not during heads-down delivery.
NEXURA Q1 OKR
O: Establish Nexura as the default discovery layer for the Intuition ecosystem.
KR1: 500 wallets connected in first 30 days.
KR2: 10 active builder campaigns by end of Q1.
A
Agile / Scrum
Iterative Delivery Framework
Organizes work into 2-week sprints with planning, daily standups, sprint reviews, and retrospectives. Prioritizes working software over documentation.
Skip when: the project has fixed scope and deadline (use Waterfall/Prince2). Agile works poorly when "done" can't be partially shipped.
NEXURA APPLICATION
Ran a simulated 2-week sprint with full backlog, sprint ceremonies, and retrospective. Documented what I'd change: split large stories earlier, define "done" before sprint planning.
RC
Risk Register
Risk Identification & Mitigation
A living document listing known risks, their likelihood (1–5), impact (1–5), risk score (L×I), mitigation strategy, and owner. Reviewed every sprint or phase.
Never skip it. A 30-minute risk exercise at kickoff saves weeks of firefighting. Even a 5-row register is better than none.
NEXURA RISKS IDENTIFIED
Smart contract exploit (L:2, I:5) → third-party audit required pre-launch. Low builder adoption (L:3, I:4) → builder incentives in Studio, concierge onboarding for first 10 builders.
What I Work With

Toolbox

Tools I've practiced with, and where each one fits in a real workflow.

Linear
Project Tracking
Sprint management, issue tracking, roadmap views. The PM's command center for day-to-day delivery.
Used in sprint simulation
Notion
Documentation & Wiki
PRDs, knowledge base, project charters, risk registers. Team's single source of truth.
Primary PRD workspace
Jira
Agile Board
Backlog grooming, sprint boards, burndown tracking. Industry standard for Agile teams.
Practiced in sprint simulation
Dune Analytics
Web3 Analytics
On-chain data querying. Track wallet activity, token flows, protocol usage. Essential for Web3 PM metrics.
Nexura metrics planning
Snapshot
Governance Voting
Off-chain governance proposals and voting for Web3 protocols. Used to manage veTRUST governance design.
Nexura governance design
Dework
Web3 Task Management
Bounties, contributor management, and project coordination for decentralized teams. The Jira of Web3.
Builder workflow design
Slack
Team Communication
Async communication, channel architecture for large teams. Comms plan design across stakeholder groups.
Stakeholder comms plan
Figma
Design Collaboration
Reading wireframes and prototypes, annotating PM requirements directly on designs, collaborating with product designers.
Studio UX review
Claude (Anthropic)
AI Product Assistant
Research, PRD drafting, framework application, ideation, and documentation support. Used throughout the Nexura product build process.
Nexura PRD and portfolio
Why Hire Me

What I Bring

Here's what working with me actually looks like, and what I'm looking for.

I built a product.
Give me yours to build next.

Most people learning PM read case studies. I built Nexura from scratch. Wrote the PRD, designed the governance system, built the roadmap, and made real product trade-offs with real reasoning. That's not a project exercise. That's a product.

I specialize in Web3 and STEM environments because that's where I've put in the depth. I understand token mechanics, on-chain data, community governance, and the unique challenges of building for crypto-native users.

I learn fast, I document everything, and I ask the right questions before writing a single requirement. I won't need 6 months to ramp. I'll be shipping in week one.

Open to

Junior Product Manager Project Coordinator Web3 PM Product Operations DAO Contributor Community DAO
+

I make decisions with evidence

Every feature, priority, or trade-off I make is documented with reasoning. You'll always know why, not just what.

S

I own the full scope

From vision to sprint backlog to stakeholder comms. I don't need things handed to me. I build the system around the work.

W3

Web3-native thinking

I understand tokenomics, governance, on-chain metrics, and how to build for users who are also stakeholders. That combination is rare at this level.

T

Actively building technical skills

I'm currently learning frontend development (HTML → JavaScript) alongside PM work. I'll be the PM who can have real conversations with your engineers.

Let's build
something real.

Open to roles, contracts, DAO contributions, and project collaborations.

Email Me LinkedIn Twitter / X Check Resume