# data[].attributes.body
Growth's audit of these capabilities and +1 that this is representative of the market's key needs.

# data[].attributes.body
Prioritization, particularly which order we should extend our capabilities in. Which ones should we do in 20, 21 and 22?

# data[].attributes.body
I love that we're aligning JFF to actual platform capabilities

# data[].attributes.body
What does our platform need to do to sign and retain partners in 20.0 and beyond? How aligned are these stories?

# data[].attributes.body
What are the criteria for success along these rows?

# data[].attributes.headline
Like that we are getting to the gap analysis using the edreimagined framework!

# data[].attributes.subject
Like that we are getting to the gap analysis using the edreimagined framework!

# data[].attributes.body
I wish this had a more holistic set of solutions represented in the 18.2 and 19.0. Not yet clear to me where services or enabling conditions are represented on this

# data[].attributes.headline
Wonder how we combine this with all the other inputs we have to inform 20.0

# data[].attributes.subject
Wonder how we combine this with all the other inputs we have to inform 20.0

# data[].attributes.body
Seeing the platform from a pedagogy perspective, rather than a feature-based one

# data[].attributes.headline
Like the specificity to which we're doing this gap analysis

# data[].attributes.subject
Like the specificity to which we're doing this gap analysis

# data[].attributes.body
The addition of detail to the EdReimagined pillars, especially aligned to the product and platform.

# data[].attributes.headline
Wish we also see what isn't there or the opportunities - we have the high level gaps, which are great, but perhaps knowing what is keeping something from being green would help

# data[].attributes.subject
Wish we also see what isn't there or the opportunities - we have the high level gaps, which are great, but perhaps knowing what is keeping something from being green would help

# data[].attributes.headline
Prioritization, and then from there we can figure out the clusters of dependent capabilities that we should be focusing on. 

# data[].attributes.subject
Prioritization, and then from there we can figure out the clusters of dependent capabilities that we should be focusing on. 

# data[].attributes.body
Add services, or tease out what is provided by the product and what by services

# data[].attributes.body
Not just prioritization, but sequencing. They're currently presented as a flat list, but some of them probably need to happen before others (e.g. some aspects of learner agency don't depend on student-facing progress views, but others might).

# data[].attributes.body
How do we distinguish the must-haves from the nice-to-haves, and does the timescale factor in to this categorization?

# data[].attributes.body
I like the idea of unpacking this further in how we'd use it. I want more time to do those thought exercises to inform how we build this out.

# data[].attributes.body
Wish there were examples of what the story represents to really understand the enablement.

# data[].attributes.body
I like that CPG is going deeper into our platform and helping identify what it can/can't do.

# data[].attributes.headline
+1 to alignment with growth and what we need to sign + retain partners. 

# data[].attributes.subject
+1 to alignment with growth and what we need to sign + retain partners. 

# data[].attributes.body
I wish we can merge in actual usage data (even anecdotal) so we can see which capabilities we have are really having impact, and which ones are merely theoretical.

# data[].attributes.body
I wish there were tangible use cases connected together across the educator enablements - where are we getting 5+ of this with one feature?

# data[].attributes.body
What would this look like if it was put in the context of a product/platform map?

# data[].attributes.body
Metrics of success

# data[].attributes.body
There's A LOT here. How might we focus our efforts so we don't spread our selves to oblivion.