(.Get "title")
We use personas to communicate and summarize research about the various types of users Frontline serves. Personas help us build products for people and their needs, rather than generalized use cases.

Director of Administration

Also known as: Superintendent/CEO

Buyer Persona

The Director of Administration is responsible for all decisions around regular and special education programs, strategic planning, spending, staff and facilities. She ensures the district is complaint with state and federal regulations. She often has the final decision on purchasing the district’s software. The Director of Administration is responsible for maintaining the school board’s budgetary guidelines so pricing and return on investment are key factors for her. She strives to maintain healthy relationships with the school board and district staff/employees.

Usage Patterns

The Director of Administration is heavily involved in sales demos and purchasing discussions. Outside of this interaction, her use and understanding of our platform will be limited. High-level functionality like dashboards and reporting tools will have a much bigger impact on her than the overall user experience.

Responsibilities

  • Final buying decision for the district’s software needs
  • Ensuring the school board understands the overall activities of the district
  • Responsible for maintaining the school board’s budget guidelines
  • Ensuring the district staff has the proper toolset(s) to perform their job

Software Needs

  • System Uptime — needs vendors to meet performance requirements
  • Reliability — needs systems to be secure and reliable
  • Data Security — needs reliable, stable vendors
  • Value — needs high ROI through tools like dashboards and reports

Director of Curriculum

Also known as: Director of Instruction, Director of Assessment

Buyer Persona

The Director of Curriculum provide leadership and vision in the development, and implementation of the district’s curriculum and student services. She is responsible for defining long-term direction as well as on-going review and evaluation of all instructional services, federal programs, career and technical education services, assessment, research and evaluation services. She is involved in the review and purchasing of the district’s software. She is searching for software that offers a comprehensive feature set that addresses a broad range of curriculum needs.

Usage Patterns

The Director of Curriculum is involved in sales demos and purchasing discussions. She is not an everyday user of our products but does frequently access dashboard and reports to monitor the district’s curriculum-based services. Informative dashboards and flexible reporting tools will have a big impact on her overall user experience.

Responsibilities

  • Coordinate the development, implementation, and evaluation of comprehensive plan (both District and building plans)
  • Prepare and create the School Instructional Calendar
  • On-going review and evaluation of all curriculum-based services
  • Manage the district’s curriculum budget

Software Needs

  • Reliability — needs systems to be secure and reliable
  • Integrations — needs our products to work together and with other district products
  • Data Security — needs reliable, stable vendors
  • Value — needs high ROI through tools like dashboards and reports

Director of Technology

Also known as: CIO / CTO

Buyer Persona

The Director of Technology is usually one of the team members involved with purchasing decisions for the district’s software. He is also responsible for integrating our applications into the district’s existing software stack. Our platform initiative is a critical selling point for him. He wants products that offers easy integration, secure data and 99.9% uptime.

Usage Patterns

The Director of Technology is heavily involved in implementation and system integration of our products and will have a good understanding of how our platform (and individual features) function. Although he may be involved in on-going IT support, after implementation his regular / ongoing interaction w/ Frontline software will decrease.

Responsibilities

  • Understanding district technology needs and offering suggestions
  • Reducing the IT burdens of vendor products
  • Involvement with the review and purchasing process for new software
  • Implement and integrate new software with other existing systems

Software Needs

  • System Uptime — needs vendors to meet performance requirements
  • Reliability — needs systems to be secure and reliable
  • Integrations — needs our products to work together and with other district products
  • Data Security — needs reliable, stable vendors

District Administrator

Also known as: HR Director, HR Department, District-Level Secretarial Staff

User Persona

The District Administrator is a core user of our platform. She uses most features in a management / administrative role but will also use the system as an employee. The District Administrator can be involved in the evaluation of software solutions and usually part of the implementation process. Managing employee data in one location is a key differentiator to creating a enjoyable user experience for district administrators.

Usage Patterns

The District Administrator is a reoccurring user of Frontline applications. She is in and out of our platform throughout the school day, often moving between several of our applications to complete different tasks. She values ease-of-use and the ability to complete her desired tasks quickly and efficiently. Due to frequency of use, the District Administrator is often an “expert” in functionality across our products.

Responsibilities

  • Management of district’s HR tasks
  • Supporting district leadership
  • Reporting on key data points across the district

Software Needs

  • Usability — needs ease-of-use across our platform
  • Reliability — needs systems to be secure and reliable
  • Integrations — needs our products to work together and with other district products
  • Reporting — key insights across the platform
  • Notifications — needs communications when new / critical action is needed

School Administrator

Also known as: Principal, Building-Level Secretarial Staff

User Persona

The School Administrator is a core user of our platform. He uses our products in both an management / administrative role and employee role. The School Administrator may be involved in the evaluation of software solutions and is usually part of the implementation process. Managing employee data in one location is a key differentiator to creating a enjoyable user experience for district administrators.

Usage Patterns

The District Administrator is a everyday user of Frontline applications. He moves between applications throughout the school day, managing location and employee data. He values a platform which enables him to efficiently complete his tasks, allowing him to move on to other assignments. Being a frequent user, the School Administrator is often an “expert” in functionality across our products.

Responsibilities

  • Ensuring all day-to-day activities of the school run smoothly
  • Promoting development and leadership opportunities for staff
  • Leading the staff and students
  • Providing quality systems and workflows which allow the staff to succeed
  • Interacting w/ fellow school admins, staff and parents

Software Needs

  • Usability — needs ease-of-use across our platform
  • Reliability — needs systems to be secure and reliable
  • Integrations — needs our products to work together; with other district products
  • Reporting — needs key insights across the platform
  • Notifications — needs communications when new / critical action is needed

Teacher / Employee

User Persona

Although the Teacher / Employee is a core user across most of our platform, frequency of use will vary. He uses our products in an employee role. The Teacher / Employee is not involved in the evaluation or purchasing of our products. Because of this, we must proactively address his needs as his voice is often not heard by those representing her in the evaluation and purchasing process.

Usage Patterns

Usage patterns for the Teacher / Employee does vary across Frontline feature sets. Because he is often quickly completing tasks within individual feature sets, he values ease of use across the platform. A common user interface reinforced by a universal design language are critical differentiators for the Teacher / Employee. Their level of knowledge for each feature set will vary based on usage patterns.

Responsibilities

  • Executing approved lesson plans students
  • Maintaining healthy relationships with administration, staff, students, parents
  • Completing district-mandated tasks with our software platform

Software Needs

  • Usability — needs ease-of-use across our platform
  • Reliability — needs systems to be secure and reliable
  • Integrations — needs our products to work together; with other district products
  • Notifications — needs communications when new / critical action is needed