# data[].attributes.headline
Clearly reference when sharing info on a product - label priority as part of OKRs

# data[].attributes.subject
Clearly reference when sharing info on a product - label priority as part of OKRs

# data[].attributes.body
Greater visibility and criteria.

# data[].attributes.body
* How much money have I got vs. how much do I need
* What are my core strengths
* Market size and growth rate
* Strength of competition and barriers to entry
* Existing brand recognition
* Channel to market
* How it fits with our business vision: Strategic fit
* How well it's meeting customer needs - and to what extent it's tapping into an unmet need. Is it new and better? Needs to create a USP
* Is the team invested and motivated +

# data[].attributes.body
Tie them to the strategies to make it clear how they align

# data[].attributes.headline
Group 4 This doesn't feel like issue at present. 

# data[].attributes.subject
Group 4 This doesn't feel like issue at present. 

# data[].attributes.body
Departmental meetings and whole company meetings seem to work well. This would also be communicated at the start of the cycle or is this likely to change? Continue to make it clear 'why' decisions are being made - plenty of clear rationale.

# data[].attributes.headline
How would this product fit into the gaps in the existing market

# data[].attributes.subject
How would this product fit into the gaps in the existing market

# data[].attributes.body
growth potential
cost to deliver
frontier market (does this create a new market?)

# data[].attributes.body
- competition analysis
- potential market size
- corporate responsibility
- unique value proposition
- return on investment
- market needs/actual needs
- go-to-market strategy

# data[].attributes.headline
OKRs help in making this transparent - high level objectives are clear  - need to know what business constraints, strategy fit is/high-level success criteria - so team can work autonmously

# data[].attributes.subject
OKRs help in making this transparent - high level objectives are clear  - need to know what business constraints, strategy fit is/high-level success criteria - so team can work autonmously

# data[].attributes.headline
Does it seem like the sort of product that might fit in in the future (5 or 10 yrs)? 

# data[].attributes.subject
Does it seem like the sort of product that might fit in in the future (5 or 10 yrs)? 

# data[].attributes.body
Continue inputting into OKRs

# data[].attributes.body
Access to clear product vision from the start

# data[].attributes.body
Take a longer term view. Go for high reach so we can get a bigger market share and hence more revenue in the long term.

# data[].attributes.headline
Map where products are in relation to each other - so that any strategy decisions made are less of a surprise

# data[].attributes.subject
Map where products are in relation to each other - so that any strategy decisions made are less of a surprise

# data[].attributes.body
Currently able to input into own product (but not other products - is this needed?)

# data[].attributes.body
Clear goals and objectives

# data[].attributes.headline
How are competitors planning to fill that gap in the future?

# data[].attributes.subject
How are competitors planning to fill that gap in the future?

# data[].attributes.body
Giving opportunities for developers to become involved in opportunity stages (if they want to)

# data[].attributes.headline
Most people are focused on a/their product - determined at start of cycle. Less worried about things you're not working on (PO). But it can be helpful for people to know about how the products relate to each other in terms of priority - could give priority ratings e.g. 1-10.

# data[].attributes.subject
Most people are focused on a/their product - determined at start of cycle. Less worried about things you're not working on (PO). But it can be helpful for people to know about how the products relate to each other in terms of priority - could give priority ratings e.g. 1-10.

# data[].attributes.body
Do more hackathons (ones that are likely to lead to new products / uncover opportunities

# data[].attributes.body
Sharing the framework for decision making

# data[].attributes.headline
Ask the people who we think are going to be using the product

# data[].attributes.subject
Ask the people who we think are going to be using the product

# data[].attributes.headline
Research the market with a view to the future

# data[].attributes.subject
Research the market with a view to the future

# data[].attributes.headline
This doesnt feel like an issue at the moment - the info is there to access if we want to

# data[].attributes.subject
This doesnt feel like an issue at the moment - the info is there to access if we want to

# data[].attributes.headline
Look at the values of different generations

# data[].attributes.subject
Look at the values of different generations

# data[].attributes.body
Moving towards product decisions being based more on our actual user research / feedback, than hypothetical / uncertain financial projections

# data[].attributes.headline
Think about 'real' or pragmatic motivations for people to buy the product

# data[].attributes.subject
Think about 'real' or pragmatic motivations for people to buy the product

# data[].attributes.headline
We are involved in the tech side but how people learn and assessment is a black box to some developers. We do have an input from the tech perspective but not further  upstream.  

# data[].attributes.subject
We are involved in the tech side but how people learn and assessment is a black box to some developers. We do have an input from the tech perspective but not further  upstream.  

# data[].attributes.body
Be consulted for my opinion.

# data[].attributes.body
Communicating to NPD itself?
-
Or to senior leadership?
- Evaluate how well it aligns with the strategy

# data[].attributes.body
Revisiting OKRs and how these push forward to the goals

# data[].attributes.headline
Take a longer term view of revenue - difficult to sell digital

# data[].attributes.subject
Take a longer term view of revenue - difficult to sell digital

# data[].attributes.headline
Weigh up social factors e.g. attention span

# data[].attributes.subject
Weigh up social factors e.g. attention span

# data[].attributes.body
More analysis of the market (so what Pearson have gone digital - we need to ask more of the 'so whats')

# data[].attributes.body
What is the size of bet? Time boxing and decision to reinvest

# data[].attributes.headline
 Group 4 Clarity about what we are able to communicate

# data[].attributes.subject
 Group 4 Clarity about what we are able to communicate

# data[].attributes.body
Product team more empowered to make decisions about the fate of their products

# data[].attributes.body
Reduce top down decision making ie Propositions strategy is already decided, without input from product teams

# data[].attributes.headline
Involve the people who are working on the product in decision-making

# data[].attributes.subject
Involve the people who are working on the product in decision-making

# data[].attributes.body
- Create a dedicated channel

# data[].attributes.headline
Could destabilise/be unsettling if people working on a product are 

# data[].attributes.subject
Could destabilise/be unsettling if people working on a product are 

# data[].attributes.body
If own money - efficiency and responsible with money

# data[].attributes.body
Sometimes it feels political, loudest voice wins, rather than rational/logical

# data[].attributes.body
There should be less need to communicate clearly each cycle, communication should be ongoing, people should just know and be onboard

# data[].attributes.body
If we had more customer insight/what competition are doing, it would feel more natural and easier to understand what's happening. Market context should be a starting point, but we never seem to get to that level of detail. Disjointed, never put together to make the picture.