Features and Functions
The possibilities for features and functions in a Parent Portal are only limited by your imagination and your resources. And for every feature that is designed for one purpose, someone will figure out a new and different way of using it when they have a need.
One of the things the research tells us about parent engagement is that the role of parent changes somewhat as our children move through the grades. As they mature, so does the child-parent relationship mature. That is not to say that parent engagement should decline (which is what is often evidenced in our schools) but rather the nature of that engagement will change. So it is helpful to consider what is useful for ALL parents and also to consider features that may be specific to parents of children in particular grade levels and needs.
You can gather the requirements for features and functions by talking to those who will use the Parent Portal. Asking people to tell their stories is a great way to create an understanding of what the needs are[*]. You can gather these stories in face to face conversations or online discussions.
Here are the stories of three parents (Sally, George and Alicia), a teacher (Jon), a principal (Genevieve), a finance specialist (Karl) and a school trustee (Donna). You could use their stories as discussion starters when identifying the features and functions you want to have in your Portal. The cartoons are meant to act like storyboards. You could create your own storyboards with the people in your own school or district.
The Power of Stories – Could This Be Your District?
|
|---|
|
Meet the parents and staff working together on this district’s Parent Portal.
The Parents’ StoriesHere are some storyboards from the perspective of Sally, an elementary school parent, George, a middle school parent, and Alicia, a high school parent. First, let them introduce themselves.
And here are a couple of stories about Sally. Each describes an idea or an issue about the Parent Portal.
Other parents have also had ideas about what they would like to see in a Parent Portal. Comments from elementary school parents: Comments from middle/junior high school parents: Comments from high school parents: Comments from all parents: The Teacher’s StoryHere is a storyboard from the perspective of a teacher:
Here are some other teacher comments: The Principal’s StoryHere is a storyboard from the perspective of a principal:
Here are some other principal comments: The Trustee’s StoryHere is a storyboard from the perspective of a trustee:
Here are some other trustee comments:
The District Staff StoryHere is a storyboard from the perspective of district staff:
Here are some other district staff comments:
|
With your stories in hand you can describe the features and functions you need. But ifyou do not know what a Portal can do, it can be helpful to loo at what other schools and districts have implemented (see What Other School Districts are Using for examples). Then you will have a better sense of how to describe the feature you want, such as email, discussion or online fee payment.
Probably your biggest challenge will be prioritizing what should be done first. Consider releasing groups of features targeted to specific groups of end users. Or you may choose to release the features that make the most difference to your parent engagement strategy. Or you may choose to implement those features first that will save money or simplify a work flow.
Just know that you cannot do everything at once. You will need to find criteria that will help you choose. And be sure to communicate not only the decisions, but how you are making them. Knowing the criteria for decision-making will create buy-in with all your end users.
Download the Requirements Sheet template for use in recording your information.
[*]See the Resources Section for references about using stories to define requirements.










