Skip to main content
Back to Work

Lecture Buddy

Managing the product lifecycle of an AI-powered university assistant, from product direction and prioritisation to requirements, development delivery, operations and growth.

Product ManagementEnd-to-End Product Management · Product Strategy · Product Delivery · Conversational UX · AI Product Management · Product Operations
Company
GrandGale Technologies
Initial deployment
Usmanu Danfodiyo University, Sokoto (UDUS)
Product
WhatsApp-based AI university assistant
Case Study Contents (14)
01

Project overview

Lecture Buddy is an AI-powered university assistant at GrandGale Technologies designed to help students and university communities access academic information, navigate their institutions and interact with useful university services through WhatsApp.

The product is designed with a broader multi-university market in mind, aiming to serve students and university stakeholders across different institutions. Usmanu Danfodiyo University, Sokoto (UDUS) serves as its initial deployment environment, providing an opportunity to introduce the product to real users, understand institutional needs and develop the platform through practical experience so it can eventually support other universities.

I manage Lecture Buddy across its product lifecycle, connecting product direction, planning, stakeholder requirements, user experience, development coordination, operational needs and growth.

My responsibility extends beyond individual features or technical issues. It involves determining what the product should become, deciding what needs to be built or improved, translating those decisions into actionable specifications and managing the product’s continuous development alongside the engineering and wider team.

02

The product challenge

Building a useful university assistant involves more than connecting an AI model to WhatsApp.

Students need reliable information, useful interactions and services that address real academic and campus needs. Administrators and other university stakeholders need workflows that support the management of academic information and institutional operations. Over time, the product must also accommodate differing university structures, programmes, academic processes and information requirements.

This creates several interconnected product challenges:

  • —Identifying the most valuable problems to solve for university communities.
  • —Creating an experience students can understand and use without unnecessary friction.
  • —Supporting different user roles and institutional workflows.
  • —Maintaining reliable academic information and administrative processes.
  • —Ensuring AI-powered capabilities work within dependable technical systems.
  • —Balancing immediate deployment needs at UDUS with the longer-term ambition of serving multiple universities.
  • —Growing adoption while continuously improving the product.

My role is to manage these considerations as parts of one connected product rather than treating them as unrelated development requests.

03

My role: End-to-end product management

I manage the product across eight interconnected areas of product ownership, while developers and other team members carry out their respective engineering and operational responsibilities:

Responsibility areaProduct management scope
Product strategy and directionDefining the product’s purpose, understanding its target users, identifying opportunities and maintaining a direction that supports its broader university market.
Product planning and prioritisationEvaluating product needs, maintaining priorities, managing scope and deciding which improvements should receive attention based on user value, business objectives, dependencies and available resources.
Product discovery and analysisUnderstanding stakeholder and user needs, examining product usage, auditing existing capabilities, identifying friction and investigating opportunities for improvement.
Product definition and requirementsTranslating ideas and problems into product specifications, feature requirements, conversational workflows, user stories, business rules and acceptance criteria.
Product deliveryWorking with the development team throughout implementation, clarifying requirements, resolving ambiguity, reviewing progress, coordinating dependencies and managing delivery priorities.
Stakeholder managementEngaging relevant stakeholders, gathering feedback, managing expectations and aligning product decisions with business and operational needs.
Product operations and qualityManaging the product issues, administrative workflows, data requirements, technical dependencies and reliability concerns that affect the user experience.
Growth and adoptionContributing to positioning, onboarding, user engagement, distribution and initiatives that help users discover and derive value from the product.

These responsibilities are closely linked. Decisions in one area regularly affect several others, making continuous product oversight essential.

04

Establishing product direction and scope

Lecture Buddy brings together academic assistance, campus information and university-related services through a familiar communication channel.

Its product direction is broader than providing answers to isolated student questions. The longer-term ambition is to build a dependable digital assistant capable of supporting university communities across different institutions, with the initial UDUS deployment serving as the practical starting point for learning and platform development.

Across the lifecycle, product scope has encompassed capabilities and workflows relating to:

  • —Academic information and student support.
  • —Campus navigation and venue discovery.
  • —Timetable management.
  • —Learning resources and practice activities.
  • —Notifications and university communications.
  • —Class Representative workflows.
  • —Academic data and administrative management.
  • —AI-powered conversational interactions.

Managing this scope requires balancing the broader multi-university product vision with what can realistically be prioritised and delivered at each stage—building a foundation that can scale beyond its initial deployment without losing focus on immediate student needs at UDUS.

05

Managing product discovery, audits and prioritisation

Rather than relying on isolated feature requests, I manage product discovery and prioritisation through ongoing observation of real usage, capability audits, stakeholder feedback and operational investigations.

Discovery and audit activities have focused on surfacing structural bottlenecks and product friction across student, institutional and technical layers:

  • —User-journey friction analysis: Examining where students experienced blockers during onboarding, programme recognition and welcome flows.
  • —Workflow bottleneck investigation: Identifying where administrative dependencies slowed down Class Representatives attempting to manage course timetables.
  • —System and capability audits: Auditing existing capabilities and production error records, including uncovering a missing background worker affecting multiple capabilities and investigating document ingestion failures.
  • —Stakeholder alignment: Gathering feedback from university and internal stakeholders to clarify operational expectations and academic rules.

Candidate improvements are then evaluated and prioritised against user value, business objectives, technical dependencies and available engineering capacity before being specified for development.

06

Managing the student experience and conversational UX

Because Lecture Buddy operates through WhatsApp, its interface is fundamentally conversational. Designing message sequences, setting clear user expectations, handling input validation, preserving conversation state and defining recovery behaviour are therefore central product decisions.

Progressive onboarding

One onboarding issue involved mandatory academic registration. Students could be required to provide their programme and academic level before accessing Lecture Buddy fully. When the system failed to recognise a valid programme, students risked becoming blocked even when trying to use unrelated capabilities such as Campus Guide.

I defined requirements for a more progressive onboarding experience that separated general product access from capabilities that genuinely depended on academic profile data:

  • —Allowing students to start using Buddy without completing every academic detail upfront.
  • —Requesting programme and academic level only when required by a specific feature.
  • —Allowing students to skip and return to incomplete profile information.
  • —Restricting only features that depend on missing academic details.
  • —Preserving open access to unrelated services such as campus navigation.

Programme recognition and onboarding consistency

I also specified improvements for programme recognition problems involving naming variations, abbreviations and incorrect programme mapping—covering name normalisation, disambiguation, correction handling and preventing silent assignment of an incorrect programme.

To address overlapping welcome messages, I defined requirements for duplicate prevention, consistent onboarding communication and optional introductory guides, with the broader objective of making interactions forgiving, predictable and useful.

07

Managing academic and institutional workflows

Lecture Buddy must support more than individual student queries; it also coordinates workflows connecting students, Class Representatives, lecturers and administrators.

One operational bottleneck occurred during timetable creation. Class Representatives could be blocked whenever a required course did not yet exist in the course database, leaving them dependent on administrators to manually create every missing record.

I defined a proposed conversational workflow enabling Class Representatives to submit missing course details directly through Buddy while preserving administrative oversight:

  1. 01A Class Rep requests a timetable for a course.
  2. 02Buddy checks whether the course already exists in the database.
  3. 03If it does not, Buddy offers to collect the missing course details.
  4. 04The Class Rep provides the department, course code, title and academic level.
  5. 05Buddy validates the inputs and creates an unverified course record.
  6. 06The conversation continues seamlessly into timetable creation.
  7. 07Administrators subsequently review and verify the newly submitted course.

The specification also covered duplicate detection, field validation, conversation-state preservation and error handling—aiming to remove an avoidable operational delay without weakening academic data governance.

08

Managing academic data and administrative processes

A university-focused assistant relies on structured, accurate institutional records. I have managed product requirements across three connected administrative workflows:

Administrative processDefined requirements and business rules
Academic session managementEnabled administrators to deactivate previous academic sessions without losing historical records, distinguishing active operational data from historical archives so inactive sessions do not appear in current workflows.
Student progression and migrationDefined migration rules for students advancing between academic levels or graduating based on programme duration—for example, distinguishing a 400-level student graduating from a four-year programme versus progressing to 500 level in a five-year programme—alongside historical preservation, duplicate prevention, promotion/graduation count previews, exception reporting, manual review and recovery handling.
Programme verification and record correctionSpecified workflows for reviewing unverified programmes, correcting student programme associations and ensuring dependent product features reflect updated records.

Together, these specifications illustrate how institutional data rules must be managed alongside the student-facing conversational experience.

09

Managing AI capabilities and technical product reliability

An AI-powered product depends on more than conversational prompts; its usefulness relies equally on dependable model integrations, background workers, document processing, storage and retrieval.

A production incident involving document ingestion highlighted this operational dependency. A background worker was attempting to invoke a configured AI model identifier that the provider could not resolve, producing a 404 model-not-found failure across the affected task and approximately 50 matching error records. A wider capability audit also identified a missing background worker affecting multiple product capabilities.

Rather than treating the incident as an isolated configuration change, I defined end-to-end validation requirements covering the complete document-processing pipeline for the engineering team:

  • —Model configuration verification.
  • —Document upload and format validation.
  • —Text extraction reliability.
  • —AI processing execution.
  • —Storage and retrieval consistency.
  • —Processing status visibility.
  • —Retry behaviour for transient failures.
  • —Failed-document recovery paths.
  • —Duplicate processing prevention.
  • —Production validation checks.

This reinforced the necessity of managing AI technical reliability as a core user experience and operational concern alongside development.

10

Managing product adoption and growth

Even a well-structured product must reach its intended audience and communicate clear value quickly. I have contributed to Lecture Buddy’s positioning, onboarding flows and adoption planning.

Positioning and entry-point messaging

Under the campaign direction “Your campus life just got a Buddy”, initial messaging deliberately prioritised Campus Guide as an immediate, intuitive entry point rather than attempting to introduce every capability at once—supported by messages such as “Lost on campus? Ask Buddy.” and “Your complete campus assistant on WhatsApp.”

Distribution and institutional onboarding

Planned distribution channels encompassed student WhatsApp groups, Class Representatives, campus ambassadors, hostel gate banners, admission hall flyers and social media. I also worked on Class Representative recruitment and onboarding communications—covering registration, application follow-up, approval messaging and getting-started instructions.

Across growth planning, the core focus has been connecting discovery, registration, approval, first interaction and meaningful ongoing use—recognising that a signup does not equal an activated user, and an available feature is not yet an adopted capability.

11

Managing continuous product delivery

An ongoing part of my role is ensuring product decisions become clear, testable work that developers can implement without unnecessary ambiguity.

My delivery coordination responsibilities include:

  • —Breaking down product initiatives into manageable increments.
  • —Writing and refining development requirements.
  • —Defining expected system behaviour and acceptance criteria.
  • —Identifying technical and workflow dependencies as well as edge cases.
  • —Clarifying implementation questions from developers.
  • —Coordinating stakeholder feedback and operational input.
  • —Reviewing implemented work against intended requirements.
  • —Managing scope changes and competing priorities.
  • —Investigating and documenting issues requiring correction.

The objective is not merely to keep a backlog populated, but to maintain alignment between product direction and engineering execution so the team understands what matters, why it matters and what successful behaviour looks like.

12

My product management approach

My approach to managing Lecture Buddy follows a continuous product lifecycle connecting strategic intent to engineering delivery and operational feedback:

  1. 01Understand the product, its users and business objectives.
  2. 02Gather evidence from user behaviour, stakeholder feedback and product operations.
  3. 03Identify and evaluate problems and opportunities.
  4. 04Set priorities and define the next product direction.
  5. 05Translate priorities into clear requirements and delivery plans.
  6. 06Coordinate implementation with the development team.
  7. 07Review the result against the intended behaviour.
  8. 08Learn from usage and operational feedback.
  9. 09Refine priorities and continue improving the product.

Treating product management as a closed loop ensures oversight continues beyond initial feature definition.

13

What this experience demonstrates

Managing Lecture Buddy has provided practical, lifecycle-wide experience across key product management competencies:

  • —Product ownership: Maintaining ongoing responsibility for product direction and continuous development.
  • —Product strategy: Connecting immediate decisions at UDUS to a broader multi-university platform vision.
  • —Product planning: Evaluating opportunities, setting priorities and managing evolving scope.
  • —Product discovery: Using audits, error investigations, user behaviour and stakeholder feedback to surface problems.
  • —Conversational UX: Designing forgiving user journeys and state-aware interaction rules for WhatsApp.
  • —Requirements engineering: Translating institutional and user needs into structured development specifications.
  • —Product delivery: Coordinating implementation, clarifying edge cases and reviewing builds with developers.
  • —AI product management: Managing model configurations, background processing and operational reliability as part of the product experience.
  • —Stakeholder management: Aligning business, academic and operational requirements.
  • —Growth and adoption: Connecting positioning, onboarding and distribution channels to user activation.
14

Reflection

Managing Lecture Buddy has reinforced a central product principle: a product is not defined by the number of features it contains, but by how effectively it solves meaningful problems for its users.

An AI university assistant may encompass many capabilities—academic support, campus navigation, timetables, administrative data management and document processing—but those capabilities only create value when they operate together within a reliable, understandable experience.

The work requires continually balancing student needs, institutional rules, business priorities and technical realities while keeping a longer-term multi-university direction in view. It has deepened my experience in managing the complete product lifecycle, from shaping direction and specifications to coordinating how the product is built, evaluated and improved.

Scope and evidence note: This case study reflects my ongoing end-to-end product management responsibilities for Lecture Buddy at GrandGale Technologies, with UDUS serving as the initial deployment environment. Broader multi-university expansion remains a forward-looking product direction rather than an existing multi-campus deployment. Individual engineering implementation and operational tasks are carried out by the development team and relevant contributors, and specified workflows or investigations are distinguished from confirmed releases where verified outcome metrics are not available.

Start a conversation

If you are navigating a product challenge, planning an initiative that needs structured delivery, or organising an event, I welcome thoughtful enquiries.

Open for conversations regarding

  • 01Product and project opportunities
  • 02Collaboration
  • 03Advisory and consulting engagements
  • 04Speaking and workshops
  • 05Other relevant professional enquiries