The Bloom Challenge
Six courses. Six real decisions. Discover how you think.
Step into Meera Sharma's workday — a Mumbai operations analyst navigating AI, data, time, technology, systems, and responsibility. Each scenario tests a different kind of professional thinking. No tricks. No timer. Just decisions that reveal where you are — and where you could go.
Most professionals discover at least one blind spot.
The Vendor Email
Meera's manager asks her to use AI to draft a follow-up email to a vendor in Pune who delivered faulty packaging materials. The shipment affected 3 client orders. Meera needs to be firm but professional — the vendor relationship matters.
She opens her AI assistant and types a prompt. Which approach would you take?
This is Day 1 of our Prompt Engineering Certificate — transforming vague questions into precise instructions. You learn to specify goal, output format, constraints, and tone so the AI has no room to guess.
The Dashboard Deception
In a Monday morning meeting, Meera's department head presents a bar chart showing "AI Tool Adoption Up 340% This Quarter." He is using it to justify a ₹15 lakh budget request for new AI tools.
Meera looks at the chart more carefully. The numbers behind the headline: Q1 had 5 employees using AI tools. Q2 has 22. The company has 800 employees total. What problems do you see?
Select every problem you can identify with this data presentation:
This is what you would learn in our Data Literacy Certificate — seeing what data hides, not just what it shows. Small base numbers make percentages meaningless. The critical question is always: "What does the data actually show vs. what is being claimed?"
The Calendar Audit
It is Sunday evening. Meera opens her calendar for Monday and sees 7 items. She has a maximum of 8 productive hours. A Bloom-level professional does not just fill calendars — they design days. Click each item (or drag on desktop) to assign it to one of three buckets.
Deep work — guard this time
Reactive tasks — group together
Does this need to happen today?
This is what our Time Management Certificate teaches — designing days instead of filling calendars. Protect deep work blocks. Batch reactive tasks into windows. Question every meeting that lacks a clear purpose or could be an email.
The Vendor Pitch
A vendor presents NovaTrans with a ₹40 lakh "blockchain-powered supply chain visibility platform." The pitch deck promises "immutable tracking," "decentralised trust," and "smart contract automation." The VP of Operations is excited.
Meera is asked for her assessment. How does she respond?
This is what our Blockchain & Crypto Masterclass teaches — separating genuine distributed-ledger value from buzzword marketing. The key question is never “Is blockchain good?” but “What problem are we solving, and is this the simplest technology that solves it?”
The GST System
Meera's manager says: "Can you set up an AI to handle our monthly GST compliance review? I want it to check invoices, flag discrepancies, and generate the filing summary."
Building a reliable AI system is not the same as using AI once. An orchestrator designs repeatable, verifiable workflows. Which components would you include in this system?
Select the components you would include in the system design:
This is what our 21-Day AI Orchestration Course teaches — the difference between using AI and orchestrating AI. An orchestrator decomposes tasks, designs prompt templates, builds verification checkpoints, creates escalation paths, defines success criteria, and tests before deployment. The "single master prompt" and "auto-file" options represent the user mindset; the rest represents the orchestrator mindset.
The Optimisation Trap
NovaTrans deployed an AI-powered route optimisation system three months ago. The dashboard numbers look impressive. But Meera has been hearing complaints from the warehouse team. She pulls the full picture.
What second- and third-order effects can you identify? Select all that apply:
This is what our Systems Thinking Certificate teaches — seeing second- and third-order effects, identifying feedback loops, and understanding that optimising one part of a system often creates pressure elsewhere. The AI was not broken; it was doing exactly what it was told. The failure was in defining what "success" meant without considering the full system.
out of 12 points
Your Thinking Profile
How you approached each domain
Want a detailed breakdown of your thinking profile? We will send a personalised analysis of each dimension — free.
Saved — we will send your breakdown when the feature launches.