User Personas

Note: These user personas are specific to software development needs. Looking for our descriptive user profiles specific to program like EPI? See here: Vaccine User Profiles and here External User Profiles

Persona Background

User-centered design approach is important to the development of OpenLMIS.  The following personas are designed to help the development team in understanding the viewpoint and experience of the users. A persona is depicted as a specific person but is not a real individual; rather, it is synthesized from observations and input from various stakeholders across multiple countries. 

We can use these personas to:

  • to build empathy and clear expectations of the user experience
  • develop focus to aid decision making and consensus building
  • communicate and form consensus
  • make and defend decisions
  • measure effectiveness
  • give clear expectations of the user's expectations
  • justify decisions about product design, development, and strategy

External User Profiles

Looking for our descriptive user profiles specific to a program? See the Vaccine User Profiles and External User Profiles.

The profiles are how we talk about different types of users when we are doing demos, presentations, and talking with external (non-software dev) stakeholders about OpenLMIS functionality. The reason we have split these out from the other personas is because the software development personas deal more with permissions and magnitude of data being consumed by each persona, whereas the external user profiles deal more with specific roles that the profiles have within the supply chain. 

Internal User Personas

These internal personas are to support development, making non functional performance goals and testing of the system. They are NOT intended to be descriptive of the roles that different managers/officers/health workers play within the supply chain.  We are not using names like storeroom manager so that we can be very specific about what service is being used or leveraged.

Our domains/services are:

  1. Requisition 
  2. Stock Management
  3. Fulfillment / Orders
  4. CCE
  5. Administration
  6. Reporting (Reporting and Analytics)


We will have three levels:

  • High, Medium, Low
    • High volume:
    • Medium volume:
    • Low volume:

The internal user personas are listed below:

 

Stock Management

Requisitions

Fulfillment / Orders

CCE

Admin

High

Sulu

  • Responsible for monitoring the health of the supply chain
  • View stock levels across multiple facilities

 Apu

For multiple facilities:

  • Approves or Rejects

Philomena

  • Single order fulfillment by my facility

Chappie

  • View across multiple facilities

Adam

  • all rights

 



 Esther

  • Convert to order for external fulfillment (via FTP or printing PDF)

 

 

Med

Spock

  • Track stock movements at my facility
    • Adjust stock via a physical inventory
    • Adjust stock level via an adjustment (i.e. wastage)
    • Record a simple issue
    • Record a simple receive 
  • POD receive and reject stock
  • Initiate/submit/delete a regular and emergency stock based requisition for my facility

Raquel

For multiple facilities:

  • Initiate/Submit
  • Authorize

A non stock based regular and emergency requisition

Phil

  • Fulfill multiple orders at once (to do rationing or a distribution)

CeCe

  • Edit CCE inventory details
  • Assign inventory

 

 


 Arthur

For one or multiple facilities:

  • Authorizes

A non stock based requisition

 

 

 

Low

Sophie

  • Would like the following to be offline accessible
  • Track stock movements at my facility
    • Adjust stock via a physical inventory
    • Adjust stock level via an adjustment (i.e. wastage)
    • Record a simple issue
    • Record a simple receive 
  • POD receive and reject stock
  • Initiate a regular and emergency stock based requisition for my facility

 Roy

One facility (home facility)

  • Submits

a non stock based regular and emergency requisition


Cy

  • Mobile
  • Update CCE functionality

 


  •