#prfaq examples

[prfaq-examples]

Learning PRFAQ by Example

Starting with examples is the most effective way to learn the PRFAQ framework and Working Backwards. When you review existing PRFAQs, you immediately grasp the proper structure, tone, and level of detail needed. You see how headlines capture attention, customer quotes inspire your team, and the FAQs address the key strategic elements of the idea. Examples show you how to avoid the common pitfalls, like using too much jargon or focusing on outputs (features) instead of outcomes and benefits. Most importantly, studying example PRFAQs builds confidence by showing that they are straightforward communication tools about customer value.

[yujeannnnnnn-blog]

Process Journal_Team Aquamarine:Unit 12 Implementation Part 1

Prompt: Reflect on the methods and techniques that your group plans to use to communicate the ways that your project should be implemented and summarize those thoughts in a new post in your process journal. How do you most effectively pitch your idea to various stakeholders? How do you visually communicate the objects, environments, systems, processes, and interactions involved in your project implementation?

Because our team narrowed down on our problem statement just last week (and it was pretty far from our original problem statement), we had to have a come together, moment of truth. Except our moment of truth was actually a “full week of many late night discussions and conversation” of truth. 

The most important items that Team Aquamarine began to flesh out this week, in my opinion, are:

- User Stories

- Product positioning: Getting very clear on how Kiddeo is going to fall into the realm of digital tools used for remote learning (video conferencing vs LMS vs asynch content management)

- Information Architecture

- Alignment in general feel of product

- “Musts” for features and UX

Looking back at it now, it’s clear to me that these were the things we had to do; this is what we had to produce this week in order for the team to align and start running towards our ultimate goal. But at the beginning of the week, these objectives/internal deliverables were not clear. What we knew was that we had a narrowed down problem statement that we had confirmed was a real problem and was not currently being addressed, and that somehow we had to turn that into a revenue generating business concept.

Early on, we started writing down a list of items that we felt were important to complete this week:

- Competitive Analysis 

- Press Release FAQ Document 

- P&L 

- Thoughts on information architecture 

- "Must” features and UX 

- Visual Assets (brand identity book + individual sketches on information architecture)

Assigning owners to each of the tasks was really helpful in giving our group meetings structure and direction. Many of these deliverables actually directly led to the group gaining a clearer picture of how we are going to proceed with the product because it forced us to think from different perspectives. For example, the PRFAQ forced us to think about the customer (school districts) and how we would like the customer to react to our product. What was going to be the standout features for the customer? Can we describe it succinctly and convincingly? Another example, the sketches and the “musts” features and UX exercise we did led us directly to user stories, which we hadn’t really thought of before we individually did the “musts” brainstorm.

Many lessons learned this week. Most notably for me, competitive analysis, PRFAQ, user stories, and information architecture need to be thought on as early on as possible.