
Daniel Spithout23




















Many companies like to experiment, but most of them do not experiment in the hart of the organisation as it is risky, but with risk also comes great opportunity ... how to (safely?) experiment with your core business?

Rich Carreau
Agree totally, cultural reset strategies and leading exemplars will groom a path that gets more employees centered on this challenge

Sam Johnston
Experimentation at the core requires architectures like microservices, and I know it's something @danhushon is passionate about — particularly as we transform from legacy to hybrid to cloud.

Sam Johnston
@RCinterests To that point it's important to note that innovation isn't something that needs to be centralised; it should be in your company's DNA — which is the whole idea behind @DXCTechnology, "The Digital Transformation Company"

Chris Swan
with operational data mining (ODM) we end up doing lots of small experiments, but the incremental gains add up to a big difference

Dan Hushon
@samj we need to move from ITOps->DevOps toward NoOps quickly and teach our clients the value, microservices is just one of the friction [and consistency] improvers

Logan Wilt
I'm not sure how to implement, but I'm a huge fan of sandboxes--and setting them up to allow day to day users a safe place to accidentally "break" a new system.

Daniel Spithout
I think breaking you core assets into smaller parts, allowing you to compose new services and let other compose new services based on your assets is an interesting way to go

Faisal Siddiqi
great opportunity to plug the #DXC #OpenSourceProgram - over the years we've been able to encourage experimentation and reduce risk

Phil Grove
Most organizations need to design a safe and robust experimentation system into which experiments are conducted. @Google is one example of mainline, MS Power BI has a monthly release cycle and an ongoing idea positing/voting system - another

Sukhi Gill
The greatest risk to Enterprises today, is to NOT be adventurous enough with your innovation programme.

Lisa Braun
For everyone: an overview of our open source program--one place to get started: http://www.dxc.technology/opensource

Sam Johnston
ITOps->DevOps->NoOps — word of the day /via @DanHushon (and yes, there's plenty of shiny things to distract you with DevOps *cough*containers*cough* so keeping an eye on the NoOps goal is a good idea)

Lisa Braun
Ok this: http://www.dxc.technology/innovation/insights/112737-dxc_and_opensource @DXCTechnology

Daniel Spithout
@sukhigill I think you are absolutely right ... if a company does NOT experiment in their core systems they set them selves up for failure..

Dan Hushon
one of the first things people have to be confident in is that they can go back - quickly, once that happens experimentation becomes a much lower risk activity... #DigitalRecipes/CI/CD reality

Brian Wallace
API-enable the core, consume from the ecosystem, mash up at the persona/UX level, deploy and learn

swardley
How to safely experiment within your organisation? I'm going to suggest that it's a good idea to look at your landscape before tinkering / building APIs / making radical changes / restructuring.

Dan Hushon
@bwallac5 you mean API enable your information as information a market without volume/fluidity isn't viable. API's provide information exchange at machine speeds and scale

Sam Johnston
@sukhigill We also need to avoid celebrating failure — tolerate and learn from it for sure, but also avoid it if you can.

Brian Wallace
@DanHushon Yup. API is a route to a resource, which is useful when it contributes to an outcome. In a digital world, resources manifest as information

Daniel Spithout
@swardley I think mapping out what part of your core business is actually in the "city Planners"area of the map might be a good indication of what you want to integrate from somewhere else ..