# data[].attributes.headline
We can work quite independent when looking at the other strategies

# data[].attributes.subject
We can work quite independent when looking at the other strategies

# data[].attributes.headline
OPEX handling by team cerberus was disappointing, it looked like zero effort was done to learn anything about PCT

# data[].attributes.subject
OPEX handling by team cerberus was disappointing, it looked like zero effort was done to learn anything about PCT

# data[].attributes.body
Amazon entry creates traction but also split focus on business side: where to innovate if no extra budget than planned vs where to innovate if extra budget than planned

# data[].attributes.headline
We had one dependency related to content, but that has been resolved

# data[].attributes.subject
We had one dependency related to content, but that has been resolved

# data[].attributes.body
Future dependencies can be a challenge if we define our roadmap for H2 in coming months. Doesn't have the full picture how Agile  @ Scale will handle that situation differently than before

# data[].attributes.headline
Getting cloud decisions takes way to long due to lack of a clear owner

# data[].attributes.subject
Getting cloud decisions takes way to long due to lack of a clear owner

# data[].attributes.headline
We're quite dependent on teams fixing things in order to deploy

# data[].attributes.subject
We're quite dependent on teams fixing things in order to deploy

# data[].attributes.body
Works ok generally, but I'm still somewhat unclear about which teams do what and which dependencies exist.

Some unresolved questions (I think) about who builds what (e.g. surgical).

# data[].attributes.body
Budget approval of bol.com board is a dynamic process and difficult to predict when which outcome will be there. This impacts the innovation roadmap

# data[].attributes.headline
Cooperation with the NOPEX team could be better: we need to switch but have no alternative and no timing on when it becomes available

# data[].attributes.subject
Cooperation with the NOPEX team could be better: we need to switch but have no alternative and no timing on when it becomes available

# data[].attributes.body
Future dependencies on others teams can still be challenging since future goals are dynamic and investigated in coming period

# data[].attributes.headline
We make sure that the system is ready to calculate commissions ASAP. Audit findings will be fixed by the end of Q4.

# data[].attributes.subject
We make sure that the system is ready to calculate commissions ASAP. Audit findings will be fixed by the end of Q4.

# data[].attributes.body
Took some time to have the clear picture of our goal --> caused by distractions on business side of implementing the first change within the organization and among partners

# data[].attributes.body
Have a sufficient understanding where to go to

# data[].attributes.headline
Not having had a clear picture from the start makes predictions hard

# data[].attributes.subject
Not having had a clear picture from the start makes predictions hard

# data[].attributes.headline
We're not pokering stories (unpredictable), but doing the things that need to be done in order to fulfill a functional wish.

# data[].attributes.subject
We're not pokering stories (unpredictable), but doing the things that need to be done in order to fulfill a functional wish.

# data[].attributes.headline
Trying to move to the cloud cost us a lot of time

# data[].attributes.subject
Trying to move to the cloud cost us a lot of time

# data[].attributes.headline
By working Kanban we are not that predictable looking at it from a scrum perspective

# data[].attributes.subject
By working Kanban we are not that predictable looking at it from a scrum perspective

# data[].attributes.body
Relatively good: OPEX/maintenance on old system distracts us but we are able to focus on going forward and innovate

# data[].attributes.body
Lots of blockers in the Bol eco-system. E.g.:

Lack of documentation and information about other systems

Changes in systems that interfere with our work.

Time consuming procedures.

Unclear who makes which decisions, which makes it difficult or practically impossible to get definitive answers.

# data[].attributes.headline
We need to address the things that are uncomfortable with

# data[].attributes.subject
We need to address the things that are uncomfortable with

# data[].attributes.body
We learnt that we don't know enough about how to handle seller specific fees, deductions and surcharges to start building these components

# data[].attributes.headline
The need to grow as a team - things aren't done right by itself

# data[].attributes.subject
The need to grow as a team - things aren't done right by itself

# data[].attributes.headline
There are even changes at other IT-teams and non-IT teams impact commissions paid by our partners that we were not aware of

# data[].attributes.subject
There are even changes at other IT-teams and non-IT teams impact commissions paid by our partners that we were not aware of

# data[].attributes.body
Our general idea works, but we've had to tweak it a bit to fit business needs with the addition of brand.

# data[].attributes.headline
Managing commission change and the yearly update of the categorization within the PCT is a error prone and labor intensive

# data[].attributes.subject
Managing commission change and the yearly update of the categorization within the PCT is a error prone and labor intensive

# data[].attributes.body
We thought PCT was ticking along nicely by itself. Unfortunately it's not.

# data[].attributes.headline
Other innovations ideas for future commission model to evaluate

# data[].attributes.subject
Other innovations ideas for future commission model to evaluate

# data[].attributes.headline
Good to pick one of the options you have and start building to learn

# data[].attributes.subject
Good to pick one of the options you have and start building to learn

# data[].attributes.headline
Categorization options on high level with pro & cons and costs

# data[].attributes.subject
Categorization options on high level with pro & cons and costs

# data[].attributes.headline
What are the flaws of the current old system we phase out

# data[].attributes.subject
What are the flaws of the current old system we phase out

# data[].attributes.body
Dependencies between strategies & teams

# data[].attributes.body
How predictable are we?

# data[].attributes.body
What did we learn about past 3 months?