Aleks Drobik shares work on learning and development, product management, and building AI proof-of-concepts. A recurring example is Spark, a concept for helping people set and follow through on meaningful goals.
Most useful for early-stage AI proof-of-concept thinking, problem framing, and L&D goal-setting content.
Best for
A learning-and-development technology brand planning educational case study or workshop content.
Not for
Brands seeking proven AI product endorsements, quantified savings, or established enterprise implementation stories.
Key takeaways
They treat poor follow-through as a design problem, not simply a lack of motivation.
They turn remembered L&D frustrations into user stories, noting they are not verbatim quotes.
Their Spark business case estimates time savings but is a scenario, not an actual pitch.
Check first: Confirm their preferred partnership format, inquiry route, and audience breakdown before contacting them.
Main ideas
Treat poor follow-through as a design problem, not a lack of motivation · Turn user frustrations into needs without presenting memory as interview data · Make a business case, but label estimates and unfinished work honestly
Aleks Drobik shares work on learning and development, product management, and developing Spark, an AI goal-setting concept.
In a series of posts, they trace the work from identifying problems people have setting and following through on goals to shaping user stories and making a business case.
The posts show a practical, public learning process rather than a finished product: they say no organization is currently considering the pitch.
Ask for targeted name-search research before making broader claims about signature books, shows, businesses, or earlier work that might explain searches for the name.
These posts show how to question an AI idea before treating it as a solution.
In the Spark retrospective, Aleks separates tool gaps and workflow or process problems from supposed skill or motivation gaps, arguing that processes may be failing people rather than people lacking will.
They then turn remembered frustrations from L&D conversations into user stories, noting that they are not verbatim quotes.
In the final post, they estimate potential time savings but make clear that the business case is a scenario, not a pitch to an actual organization.
The posts pair problem framing and user needs with a candid account of what remains untested, offering a useful look at early-stage product thinking.
Ask for more examples to assess how representative this approach is of their broader work.
In posts about the Spark goal-setting concept, Drobik argues for diagnosing the conditions around a problem before choosing an AI solution.
Read more
They focus on user needs, practical barriers to getting work done, and honest limits on what a proof of concept has shown.
Treat poor follow-through as a design problem, not a lack of motivation
Aleks challenges the assumption that people fail to set goals because they lack skill or will.
Read more
Existing processes can leave people without useful support, while follow-up falls to managers.
For Spark, Aleks weighs several explanations and sees a tool gap as the strongest fit, with process gaps also contributing.
They reject motivation and skill as accountability and design issues, and reject communication breakdown because goals are already expected on a regular schedule.
Turn user frustrations into needs without presenting memory as interview data
Aleks uses user stories to connect difficulties people describe with the support they need.
Read more
They distinguish remembered themes from verbatim research: the examples were reconstructed from conversations in learning-and-development circles, not recorded quotations.
One story addresses professionals who freeze at a blank goal-setting template: they need to talk through ideas before writing.
Another describes a manager scrambling to get the team to submit goals.
Make a business case, but label estimates and unfinished work honestly
Aleks argues that a concept should connect to a plausible business benefit, while distinguishing assumptions from what has actually happened.
Read more
A calculation can help frame a case; it is not proof of savings or adoption.
For Spark, Aleks estimates that a manager preparing for eight team members’ one-to-ones twice a month could spend eight hours monthly on preparation.
The post presents reducing that time as a possibility, notes the need for training and rollout, and says there was no organization receiving the pitch.
They describe the reusable process—not demonstrated results—as the project’s current output.
Aleks describes product-management learning as useful when it changes how a project is framed.
Read more
Their posts apply that principle to Spark: examine the problem, consider its causes, and build a rationale before treating an AI concept as the answer.
After sharing an eCornell Product Management credential, Aleks says that a product-management course and a proof-of-concept course both reinforced the need to know why something is being built. Open the credential post
Start here to verify a formal grasp of professional product management standards and expertise.
Read more
Aleks Drobik recently completed a Product Management credential through eCornell, demonstrating formal training and a commitment to mastering product development methodologies. The credential provides a foundation for discussing product strategy and execution.
For brands planning a campaign
Aleks Drobik can translate complex technical solutions into market-viable products, making them a fit for consulting focused on product maturity or development cycles.
This post explains the methodology Aleks uses to scope complex problems and build strategically sound AI solutions.
Read more
Aleks Drobik applies Melissa Milloway's framework to determine whether a problem warrants an AI proof of concept. The process identifies root causes such as a tool gap, workflow bottlenecks, or process gaps, rather than assuming a lack of user will or a basic skill gap.
For brands planning a campaign
For companies considering AI solutions, Aleks can help triage potential projects and direct investment toward fundamental systemic problems rather than surface-level user issues, increasing the likelihood of successful technical implementation.
This post shows how to turn anecdotal user feedback into actionable design specifications and developer requirements.
Read more
Drawing on conversational insights from L&D circles, Aleks Drobik turns common frustrations into structured User Stories. For example, general difficulty writing a SMART goal becomes: 'As a mid-career professional, I need to be able to talk through my ideas before writing them down so I don't freeze at a blank page with only a template to guide me.' This approach turns observed behavior into a technical requirement.
For brands planning a campaign
Aleks can lead workshops or design sessions that connect qualitative customer interviews with quantitative development specifications, producing more accurate product requirements and less development waste.
This post shows how AI concept design can be grounded in tangible metrics and financial accountability, linking functionality to business impact.
Read more
In developing their solution, Spark, Aleks Drobik addresses the business case by performing 'the math' to quantify time savings. For instance, they calculate how automating goal prep saves hours monthly across a team of leaders, demonstrating the practical return on investment for management.
For brands planning a campaign
For executive-level pitches and enterprise sales, Aleks Drobik can build the narrative and financial case to move a promising proof of concept from a 'pilot' phase to a funded production deployment.
In a Spark retrospective, Aleks Drobik compares possible causes of workplace goal-setting problems: a tool gap, workflow bottleneck, process gap, skill gap, motivation issue, communications breakdown, or product defect.
Read more
They conclude that the strongest case is a tool gap, with workflow and process problems also contributing. They distinguish a design problem from a lack of employee motivation or ability.
Applies a proof-of-concept decision guide to a specific concept, Spark, and explains why some candidate causes fit better than others.
For brands planning a campaign
A learning-technology brand could consider Aleks for a case study or workshop on diagnosing an AI use case before building. The post offers a concrete framework for separating user needs from assumptions about willingness or skill.
Turning remembered user pain points into user stories
Aleks describes translating frustrations heard in learning-and-development conversations into user stories for professionals and managers.
Read more
Examples include getting stuck at a blank goal-setting template, wanting to refine goals through conversation, setting goals that are too ambitious, and leaders scrambling to secure submissions. The pain points were reconstructed from memory, not quoted verbatim.
Pairs each described pain point with a user story stating the user, need, and intended outcome.
The post says the pain points were reconstructed, not quoted word for word.
For brands planning a campaign
This is relevant to a case study on early product discovery, especially how to turn informal user feedback into testable product requirements. If adapting the example, distinguish remembered themes from verified interview quotations.
In the final step of the Spark series, Aleks estimates potential time savings using a hypothetical manager, team size, meeting frequency, and preparation time.
Read more
The post presents the calculation as an illustration and notes that adoption would require upskilling and rollout. Aleks says there was no organization receiving the pitch; the value of the exercise was a repeatable process for future projects.
Connects a proposed product benefit to a simple time calculation, then names implementation needs and the limits of the pitch.
Before using the example to support savings claims, ask for evidence from a deployed product.
For brands planning a campaign
A product or learning-technology company could consider Aleks for a proof-of-concept case study showing how to build and qualify an early business case. Label estimates as assumptions, not demonstrated savings.
Aleks shared earning an eCornell Product Management credential.
Read more
In another post, they say a product-management course and a proof-of-concept course reinforced the importance of understanding why a product is being built. They apply that learning to the Spark concept.
For brands planning a campaign
This may suit a brand seeking a creator to discuss applying structured product-learning frameworks to an early AI concept. Ask for examples before positioning Aleks as experienced in product management or claiming commercial outcomes.
Aleks Drobik says they completed an eCornell Product Management course and earned a Product Management credential from Cornell University through eCornell.
Aleks Drobik's posts work best as a step-by-step example of testing an AI idea before building it.
Read more
Start with the Spark series, which follows a goal-setting tool from problem diagnosis through user stories to a business-case estimate.
Read it in order: the diagnosis post compares possible causes of a workplace problem, the user-stories post translates frustrations into stated needs, and the closing post turns the concept into a pitch with its assumptions labelled.
A shorter post explains the product-management learning behind the approach.
The concept had no organisation receiving the pitch and no measured savings, so ask for evidence of outcomes before treating the estimates as results.
Readers interested in goal setting, employee development or early product discovery will get the most from the series, which focuses on reasoning and process rather than launch or traction.
Both write from inside people-development work, turning personal experience into reflective posts for professionals who feel stuck in a job that does not fit.
Read more
They use first-person narratives to teach rather than presenting research or data.
Desrochers writes about individual career change and personal fulfilment — leaving the wrong role, trusting your instincts and learning from mistakes — and closes with encouragement.
Drobik writes about designing a product concept: diagnosing a cause, writing user stories and building a business case.
Both document building an AI product in public and share what the process taught them, for practitioners rather than a general audience.
Read more
They mix a personal voice with practical lessons.
Herhold's posts are operating updates from a live software business — beta signups, activation, bug tickets and free credits — written for recruiters and agency owners, and end with an offer of a demo.
Drobik's are learning exercises about a concept without users, metrics or an organisation receiving it.
Both publish recurring retrospectives about building something, connect AI to a business workflow, and close with lessons and next actions.
Read more
They write candidly about limits and what did not go to plan.
Reekers writes as a founder of a funded company about growth, retention, hiring, team and customer marketing, naming colleagues and sharing real numbers.
Drobik writes about a self-directed project on goal setting and employee development, with no company behind it.
The value they claim is a repeatable process, not business results.
Aleks Drobik’s content focuses on the intersection of Learning and Development (L&D) and AI/Product Management workflow optimization.
Read more
They address organizational pain points such as establishing meaningful goal-setting processes, identifying tool gaps, and building business cases for AI proof-of-concept initiatives.
Buyers marketing software or services to L&D leadership, HR operations, or internal process improvement teams will find the content relevant.
Ask for an audience breakdown by age, gender, and job title to assess fit.
A learning-and-development technology company could consider Aleks Drobik for an educational case study or workshop on deciding whether an AI proof of concept addresses a real workplace problem.
Read more
In a post about Spark, they compare a possible tool gap with workflow and process issues, then argue that the problem is not simply employees’ skill or motivation.
Another post turns remembered L&D frustrations into user stories, while noting they are not verbatim interview quotes.
Those examples suit a campaign about careful problem framing and early product discovery.
When to choose a specialist
A company seeking a creator to endorse a proven AI product, promise quantified customer savings, or present an established enterprise implementation should look elsewhere.
Read more
The business-case post uses hypothetical assumptions about a manager’s preparation time and team size; it does not report measured savings or an organization receiving the pitch.
The reviewed partnership information documents no established sponsorship formats or inquiry route.
Ask Aleks to confirm their preferred format and how to make an inquiry before pursuing a conventional paid product endorsement.
A worked campaign example
For an L&D technology company introducing a tool for workplace goal-setting, a suitable angle would be “Before you build an AI goal-setting tool, test what is actually getting in the way.”
A short case study could follow the Spark exercise: describe the recurring goal-setting difficulty, compare tool, workflow, process, skill, and motivation explanations, then show how a team might turn the strongest evidence into user stories and a small proof-of-concept question.
Make clear that the original user-story examples came from remembered conversations, not verbatim research, and label any time-savings calculation as a hypothetical estimate.
Invite Aleks to discuss the concept and agree on scope, evidence, and any commercial terms before proposing a sponsored format.
Choose Philippe when the campaign needs a long-standing HR and career-transformation voice who can speak directly to mid-career professionals.
Read more
The posts describe more than 15 years in HR, training over 5,500 people, hosting the Career FastTrack podcast, and receiving an Innovation Award and an Inspiration Award. For an L&D technology company, that background suits a campaign about career fulfillment, employee development, or coaching-led adoption, especially if the buyer wants podcast- or workshop-style collaboration rather than a technical AI proof of concept.
Aleksandra D.'s posts tell a personal career-transformation story and offer career lessons, but do not cover AI goal-setting tools, proof-of-concept decision guides, or product discovery. For a campaign testing whether an AI tool addresses a real workplace problem, they do not offer the specific Spark case-study examples a buyer would need.
Choose Fabian when the campaign needs someone who has taken an AI product from concept to beta and can talk about activation, onboarding, and measuring user behavior.
Read more
The posts show Hyreflow reaching 150 workspaces within three weeks, 64 active workspaces in a week, an average first result in about 24 minutes, and use of PostHog and Linear. That experience fits a recruiting or HR technology buyer looking for a founder story about shipping an AI harness and turning signups into real product use.
Aleksandra D.'s Spark series covers recruitment sourcing, business development, and agency workflow, not learning-and-development goal setting. It offers product metrics and email outreach advice, but not a reusable proof-of-concept framework or user-story research.
Choose Jeff when the campaign needs an enterprise SaaS founder's view of building an AI-powered platform, customer marketing, and go-to-market execution.
Read more
The posts describe Champion's customer marketing work in the Salesforce ecosystem, 100% gross revenue retention and about 130% net revenue retention, an algorithm for identifying customer champions, and weekly retros about vision, prioritization, hiring, and customers. That fits a buyer looking for leadership lessons on scaling an AI product and a values-led company.
The posts cover customer marketing and company building, not L&D, goal-setting, or educational proof-of-concept exercises. They offer business and GTM examples, but not the problem-framing and user-story methods an L&D campaign about goal-setting or educational proof of concept needs.
Four LinkedIn posts describe Aleks Drobik’s completion of an eCornell Product Management credential and the development of Spark, an AI goal-setting proof-of-concept.
The posts trace the project from diagnosing problem causes and building user stories based on L&D professional feedback to constructing a business case using hypothetical time-savings estimates.
The posts show a focus on process, strategic thinking, and candid reporting of project limitations.