JENNIFER CHINASA AKOKOTA

Summary

Led SolarConnect from product discovery and problem validation through requirements definition, MVP design and development handoff, using 3 stakeholder/user interviews and 25+ survey responses to validate customer needs, prioritise features and shape the mobile-first product experience. Requirements and product/UX flows were handed to Development with continued clarification, while MVP scope was balanced against the broader solar-lifecycle vision.

Highlights

Summary

Owned CheckinBliss's Lagos market-entry roadmap, translating GTM strategy into a 65-working-day execution programme spanning property acquisition, qualification, validation, onboarding and listing readiness. Validated/bookable inventory progressed into downstream launch-readiness stages [exact owners TO CONFIRM], while speed of market entry was balanced against validation/bookability standards and financial constraints limited broader launch progression.

Highlights

Summary

Led supply-side product operations across sourcing, validation, onboarding and listing readiness, directly sourcing and onboarding properties and establishing structured stage-to-stage handoffs from acquisition through bookable status. Properties progressed into validation, listing and bookable-readiness workflows [exact stage owners TO CONFIRM], while inventory throughput was balanced against validation, listing quality and launch-readiness requirements.

Highlights

Summary

Translated Serene & Co's WhatsApp-led customer-management problem into a structured CRM and workflow-automation solution, defining customer lifecycle stages, product and functional requirements, acceptance criteria, customer workflows and system-interaction requirements across WhatsApp, Smart CRM and Magic Touch Automator. Requirements and workflow logic were prepared for technical/configuration owners [TO CONFIRM], while automation value was balanced against operational simplicity and integration complexity.

Highlights

Summary

Defined AI-enabled product use cases, conversational/customer flows, product requirements, expected system behaviours and CRM/integration requirements across Zidi Mini AI and the WhatsApp AI Agent Suite, translating business problems into structured product concepts and technical delivery inputs. Concepts and requirements moved toward technical implementation, testing or further planning depending on the initiative, while AI capability was balanced against usability, feasibility and unnecessary complexity.

Highlights

Summary

Developed Lorc AI's launch-phase product and GTM strategy, defining positioning, launch priorities, roadmap, timeline and budget requirements to coordinate cross-functional market-entry preparation. Launch requirements were intended to move into Product, Marketing, Sales, Operations and related workstreams [exact execution ownership TO CONFIRM], while launch ambition was balanced against product readiness, budget, time and available capacity.

Highlights

Summary

Used onboarding, adoption and operational evidence to compare friction across journeys and prioritise changes based on customer impact and delivery feasibility. Prioritised insights were handed into product planning, workflow redesign or Engineering execution, balancing customer impact against implementation feasibility.

Highlights

Summary

Analysed onboarding and adoption journeys across the AI-enabled HRTech/career platform, reviewing user journeys, onboarding steps, operational workflows and feedback to identify friction and convert it into prioritised product/process improvement opportunities. Findings were handed to Product, Engineering or Operations for implementation, while user impact was balanced against delivery effort.

Highlights

Summary

Supported product definition and improvement across skills portfolios, professional profiles and external job/learning connectivity by gathering user/business needs, reviewing platform workflows and clarifying feature expectations. Requirements and recommendations moved into design, engineering or delivery planning, while breadth across profiles, skills, jobs and learning was balanced against delivery focus.

Highlights

Summary

Defined and coordinated requirements, dependencies, user flows, data/system needs and delivery considerations for [X API/plugin integrations TO RECOVER], working with Engineering and external partners to progress [Y] integrations/features through [requirements / implementation / testing / release stage TO RECOVER]. Requirements were handed to Engineering/partners, while platform value was balanced against third-party dependency, partner constraints and technical complexity.

Highlights

Summary

Connected user feedback, customer needs and operational insights with product decisions by synthesising recurring experience issues into workflow, feature and usability improvement opportunities. Findings moved to Product, Design, Engineering or Operations, while one-off requests were distinguished from scalable product problems.

Highlights

Summary

Coordinated product-operational activities across onboarding, platform workflows, external integrations and improvement initiatives, tracking requirements, dependencies and stakeholder follow-ups across Product, Engineering, Operations and external contributors. Work moved between functional owners while JCA maintained visibility and continuity, balancing execution speed against coordination and requirement clarity.

Highlights

Summary

Led delivery coordination across 2 concurrent digital builds during a four-month engagement—the OneHux website revamp and an internal volunteer platform—coordinating requirements, development communication, review and release readiness. Clarified product inputs were handed to Development with ongoing stakeholder alignment, while parallel execution was balanced against available team capacity.

Highlights

Summary

Led discovery and solution conversations with ODS prospects, translating client needs into engagement requirements and progressing opportunities through acceptance and project commencement. Client context moved into project delivery while JCA maintained stakeholder continuity, balancing commercial responsiveness against feasible scope and delivery capacity.

Highlights

Summary

Translated business and user requirements into actionable delivery inputs throughout the development lifecycle, clarifying scope, workflows and expected system behaviour. Structured requirements were handed to Development with ongoing clarification, while requirement clarity was balanced against delivery speed.

Highlights

Summary

Managed development coordination across parallel product workstreams, tracking priorities, dependencies, communication and delivery progression. Work was routed to responsible delivery owners while JCA maintained follow-through, balancing execution momentum against dependency and capacity constraints.

Highlights

Summary

Developed the project communications plan as the first delivery artefact, establishing structured information flows, stakeholder touchpoints and cross-functional communication practices. Communication governance was designed to provide enough visibility and clarity without creating unnecessary coordination overhead.

Highlights

Summary

Initiated, developed and coordinated 1 structured ODS internship programme, defining programme structure, operational requirements and delivery coordination while connecting the initiative with the ODS vertical's broader capability/growth objectives. Programme activities moved into execution with relevant stakeholders [exact owners TO CONFIRM], while programme ambition was balanced against operating and supervision capacity.

Highlights

Summary

Analysed 3,200+ historical appointment records across 1,341 patients over 18 months and monitored approximately 255 patient visits biweekly for five months, using demand, capacity and service-flow patterns to inform scheduling and staffing decisions. Findings were handed to clinic operations/management and monitored after action, while patient demand was balanced against available clinical capacity.

Highlights

Summary

Established and analysed the clinic's first structured CRM interaction dataset across 1,058 unique customer profiles in HubSpot and Zoho, tracking 5,300+ interactions including 1,090+ bookings, follow-ups and engagement touchpoints. Insights moved into CRM and service workflows, while engagement scale was balanced against meaningful follow-up quality.

Highlights

Summary

Mapped and analysed the end-to-end patient journey across registration, consultation booking, appointment attendance and follow-up, identifying behavioural patterns, process friction and service gaps and translating findings into product/workflow improvements. Improvement requirements moved into operational/digital implementation [technical owner TO CONFIRM], while digitisation was balanced against patient/staff usability and operational practicality.

Highlights

Summary

Built a repeatable analytics workflow across Excel, Google Sheets, HubSpot and Zoho CRM, applying data cleaning/structuring, segmentation, trend analysis, KPI tracking, cohort and before/after analysis and recurring biweekly performance reviews. Decision-ready findings were handed into management, customer operations and service-delivery activities, while analytical depth was balanced against the speed required for clinic operations.

Highlights

Summary

Led MenuCard from discovery and requirements definition through UX, development coordination, testing and pilot validation, coordinating Product, Design, Engineering and QA. Requirements/designs moved into implementation and validated builds into pilot use, while MVP scope and delivery speed were balanced against product quality and readiness.

Highlights

Summary

Analysed the QR-to-order customer funnel across menu discovery, item selection, cart, ordering and payment, combining usage evidence with user feedback and usability observations to identify friction and prioritise improvements. Conversion insights were handed into Product, UX and Engineering, while conversion optimisation was balanced against usability and operational reliability.

Highlights

Summary

Defined functional requirements, business rules, payment states, validation logic, edge cases and integration requirements across the ordering/payment journey, translating restaurant/customer needs into testable system behaviour for Engineering and QA. Requirements moved to Engineering and QA with defects/questions returning for clarification, while checkout simplicity was balanced against reliability, control and exception handling; no claim is made that JCA coded payment APIs/gateway integrations.

Highlights

Summary

Designed product requirements across both sides of the platform—customer QR ordering and restaurant menu/order management—covering menu availability, search/browse, cart, ordering, payment, fulfilment and status management. Customer- and restaurant-facing requirements were handed into Design/Engineering and pilot onboarding, while customer convenience was balanced against restaurant operational control.

Highlights

Summary

Combined interviews, surveys, observation, usability testing and pilot feedback to identify restaurant/customer pain points, map end-to-end journeys and refine product requirements, UX flows and prioritised improvements. Research findings moved into Product/UX requirements and pilot iteration, while research depth was balanced against delivery momentum.

Highlights

Summary

Coordinated delivery across Product, UI/UX, Frontend, Backend, QA, DevOps, Sales and Marketing, supporting stand-ups, sprint planning, backlog refinement, testing, issue clarification and pilot-readiness activity. Requirements/priorities moved into Design/Engineering, completed functionality into QA/testing and validated builds into pilot use, while scope and stakeholder demand were balanced against engineering capacity and readiness.

Highlights

Summary

Defined and monitored product-performance signals across acquisition, QR engagement, ordering, payment and pilot behaviour using Mixpanel, Google Analytics/GA4, Power BI, Excel and Google Sheets. Product insights were handed into prioritisation, UX refinement and pilot review, while optimisation of individual metrics was balanced against the overall customer and restaurant experience.

Highlights

Summary

Supported product delivery across [X product/data initiatives TO RECOVER] by translating product objectives and user needs into structured requirements, prioritised tasks and actionable execution inputs. Requirements/priorities moved to relevant Design, Engineering, Data or QA contributors with clarification and follow-through, while scope was balanced against internship time and team capacity.

Highlights

Summary

Organised, analysed and interpreted [X+ product records/users/events TO RECOVER] using [confirmed tools TO CONFIRM], identifying [Y] trends, inconsistencies or performance signals and converting findings into [Z] summaries/insights for product stakeholders. Findings were handed into prioritisation or improvement decisions, while data completeness was balanced against decision speed.

Highlights

Summary

Contributed to product discovery and requirements definition by reviewing user/business needs, documenting requirements, features and expected outcomes and translating identified problems into clearer product responses. Requirements moved into downstream Product, Design or Engineering execution, while essential needs were balanced against desirable scope.

Highlights

Summary

Used available product data to identify patterns and recurring performance signals and translate them into structured recommendations or areas for further investigation. Recommendations moved into product review and prioritisation, while metric signals were balanced against user/business context.

Highlights

Summary

Supported coordination of product information, requirements, tasks and execution across multidisciplinary contributors by tracking task progression, organising product information, supporting communication and following up dependencies/clarification needs. Work moved between Product and technical/delivery contributors with JCA maintaining continuity, while speed was balanced against coordination quality.

Highlights

Summary

Analysed [X+ records/users/events] across [Y product initiatives] using [confirmed tools TO CONFIRM], identifying [Z priority insights] and handing findings to Product/delivery stakeholders for prioritisation and action. Analytical depth was balanced against timeliness.

Highlights

Summary

Supported [X product features/improvements] through [requirements / analysis / testing / release stage], clarifying requirements, monitoring assigned work and supporting testing/review. Validated work progressed to the next delivery stage, while delivery speed was balanced against quality and readiness.

Highlights

Summary

Gathered and analysed customer requirements across renewable-energy and IoT service engagements, clarifying pain points, usage needs, service expectations and constraints and translating them into solution requirements/delivery inputs for technical teams. Customer/business requirements were handed to technical/service teams for assessment and implementation, while customer expectations were balanced against technical capability, cost, resource availability and realistic scope.

Highlights

Summary

Coordinated [X+ renewable-energy/IoT engagements] across [Y solution categories], supporting requirements clarification, scheduling, delivery follow-through and customer communication. Aligned work was handed into technical/service execution, while delivery speed was balanced against technical-team capacity, materials/resources and service quality.

Highlights

Summary

Reviewed customer-facing/internal workflows across enquiry, assessment, scheduling, service coordination, technical delivery and post-service follow-up, identifying communication, handoff and execution gaps and supporting clearer future-state service processes. Improvements were handed to relevant operational/technical owners, while standardisation was balanced against the flexibility required by different customer/project needs.

Highlights

Summary

Coordinated business, customer and technical stakeholders throughout service delivery by clarifying commercial/customer expectations, translating requirements into operational/technical activities and tracking dependencies/follow-ups. Business/customer requirements moved into technical execution and delivery updates returned into customer communication, while commercial priorities were balanced against technical constraints.

Highlights

Summary

Supported customer relationship and service-delivery activities across [X+ accounts], maintaining communication, issue-resolution coordination and follow-up. Successful engagements could progress to post-service support/repeat business [exact renewal ownership TO CONFIRM], while customer satisfaction was balanced against pricing, technical scope, resources and delivery limits.

Highlights

Summary

Coordinated planning and execution across 4 community programme streams—Education Initiative, African Child Day, Feeding Programme and Prison Outreach—supporting programme scope, activities, timelines, logistics, stakeholder coordination and delivery follow-through. Planned responsibilities were handed to programme leads, volunteers, partners or activity owners, while programme breadth was balanced against available people, time and resources.

Highlights

Summary

Coordinated the Education Initiative across [X activities/locations TO RECOVER], supporting beneficiaries and coordinating volunteers, partners or resources. Delivery responsibilities moved to relevant activity owners while JCA maintained coordination, balancing beneficiary reach against available programme resources.

Highlights

Summary

Worked across internal teams, volunteers, community stakeholders and external partners to clarify programme needs, coordinate responsibilities and maintain alignment between programme objectives and execution. Commitments were handed to responsible activity owners with continued coordination, while stakeholder expectations and availability were balanced against agreed programme priorities.

Highlights

Summary

Monitored programme activities, resource readiness, stakeholder follow-through and execution challenges, identifying gaps and supporting adjustments to workflows, responsibilities, communication or resource coordination. Improvement actions fed into subsequent programme planning, while immediate delivery was balanced against fixing recurring process problems.

Highlights

Summary

Supported delivery of [X outreach/programme activities TO RECOVER], coordinating participant engagement, logistics, resources and follow-through. Outputs moved to beneficiaries/community stakeholders and relevant programme owners, while success was assessed through meaningful participant/beneficiary impact rather than event volume alone.

Highlights