SlideShare a Scribd company logo
» Design Without Designer
Avoid Patterns which make your system Monolithic
Modularity through
•Distributed/out Process components
•Self hosted Services/Components
Products not Programs/Projects
Decentralized Governance
Design Should Evolve
Infrastructure/Software delivery Automation
» World has always been changing, evolving in manner
that it has amazed a common man in all walks of life.
“Change” followed by “adopt to change” are the key,
that made humans innovative and showed the path to
evolve. The “guru mantra” worked in all eras, be it a
“stone age” or the world of 21st century. This is well
received in personal life, business or education and
research or any other avenues. Those who perceive the
change, make adjustments to the change "early" are
the winners in their area
Evolution.
» Promote variation, experimentation, trying new
things. Let not fear of failure stops your innovation.
» Embrace change, design for change
» Natural Selection => Accountability
» Feedback- Embrace and adopt what worked, leave
and quit what not worked. (Failures are feedback
only)
» Evolve Design, instead of spending a lot upfront, Less
Design/Architecture, more Implementation.
» Develop in-house capabilities on core components
and outsource only commodity Products . As its easy,
fast and cheaper to experiment and evolve on in-
house as compare to Vendors
» Quick plan/analyses/design, experimentation,
implementation , accountability and repeat the cycle
is the new world order of software delivery
» Main points:
˃ Avoid patterns which make your system monolithic
˃ Modularity through distributed processes/components and self-hosted services/components
˃ Products, not programs/projects
˃ Decentralized governance
˃ Design should evolve
˃ Infrastructure/software delivery automation
» De-coupled, modular design
˃ Favor micro services that perform one type of functionality
˃ Evolve and scale services as needed rather than more instances of the same large application
˃ Make components containerizable – allows greatest flexibility as far as deployments go
» Emphasis should be on products, not programs or projects
» Design should evolve as needed
˃ Things should be designed so that they are flexible – requirements will change, so design will need to
follow
˃ Allow for …?????
˃ Promote variation and experimentation.
˃ Fail fast and pivot – if something works, keep it or make it better. If it doesn’t, make it so it does or get rid
of it
˃ Don’t be married to code. Not all code works
˃ More time spent implementing, less time spent designing. Make the design a good starting point, and
change things as needed
» Software/delivery automation
˃ Need to have the deployment pipeline as automated as possible to allow for quick evolution
˃ Continuous integration and push-button deployments if possible
» Infrastructure considerations
˃ Make it as easy as possible to deploy new resources
+ Containerization, all dev dependencies like Frameworks, runtimes. Abstraction over OS
˃ Consider cloud computing
+ Already virtualized, very scalable, easy to set up new instances

More Related Content

PDF
The Design Fortress: Boosting Design Productivity and Creativity in an Agile ...
PPT
eSynergy Paul Swartout - DevOps - what is it and why is it valuable to business
PPTX
Incorporating UX into an Agile Methodology
PDF
Introduction to Kanban
PDF
Scaling UX in a maturing organisation
PPTX
DevOps - Successful Patterns
PPTX
Dev ops – what and why - Bristech - July 2016
PPTX
Being Agile
The Design Fortress: Boosting Design Productivity and Creativity in an Agile ...
eSynergy Paul Swartout - DevOps - what is it and why is it valuable to business
Incorporating UX into an Agile Methodology
Introduction to Kanban
Scaling UX in a maturing organisation
DevOps - Successful Patterns
Dev ops – what and why - Bristech - July 2016
Being Agile

What's hot (20)

PPTX
Mastering Project Management for (Salesforce) Admins
PDF
Kanban Evolutionary or Revolutionary
PPTX
Extreme Programming
PDF
Kanban - Evolutionary or Revolutionary?
PDF
Introducing Agile to Product Teams
PPTX
How to get a grip of your website (and then keep hold)
PPTX
Anti patterns
PDF
Intro to Kanban (1 Dec 2014)
PPTX
Breaking the mold: Lean Product Management and MVP in a Large Company
PPTX
DevOps for the sysadmin
PPTX
Collaborative usability observation session intro
PPTX
Gearing Startups for Success through Product Engineering
PDF
Boosting your SW development with Devops
PPT
Strategies for building successful products
PPTX
Agile Presentation_Lite
PPTX
Kasten Engineering Culture Deck
PDF
Modular UX Process
PDF
Managing Teams
PDF
IMPLEMENTATION OF SCALED AGILE AND DEVOPS
PDF
Improving conceptual understanding in development
Mastering Project Management for (Salesforce) Admins
Kanban Evolutionary or Revolutionary
Extreme Programming
Kanban - Evolutionary or Revolutionary?
Introducing Agile to Product Teams
How to get a grip of your website (and then keep hold)
Anti patterns
Intro to Kanban (1 Dec 2014)
Breaking the mold: Lean Product Management and MVP in a Large Company
DevOps for the sysadmin
Collaborative usability observation session intro
Gearing Startups for Success through Product Engineering
Boosting your SW development with Devops
Strategies for building successful products
Agile Presentation_Lite
Kasten Engineering Culture Deck
Modular UX Process
Managing Teams
IMPLEMENTATION OF SCALED AGILE AND DEVOPS
Improving conceptual understanding in development
Ad

Similar to Design without Designer (20)

PDF
ANIn Navi Mumbai Jan 2023 | Agile- 360 degree perspective by Pravin Mukhedkar
PPTX
Lean Development Presentation Slides.pptx
PPTX
Introduction to continuous delivery
PDF
Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...
PDF
Agile and semat v0.91
PDF
Agile and semat v0.91
PDF
Agile concepts for quality and process engineers for slideshare
PDF
What is agile model?Working of agile model
PPTX
Continuous Delivery: why ? where to start ? how to scale ?
PPTX
DevOps Workshops Fall 2016
PPTX
Devops Mindset Essentials
PPTX
Computing DevOp Summit
PPTX
Continuous Delivery
PPTX
Fundamentals of Agile
PPTX
A Software Engineer
PDF
Should i break it?
PDF
Lean and Kanban-based Software Development
PPTX
Lean & Agile Value Streams
KEY
Lean UX in an Agency Environment
PDF
Are you Agile enough?
ANIn Navi Mumbai Jan 2023 | Agile- 360 degree perspective by Pravin Mukhedkar
Lean Development Presentation Slides.pptx
Introduction to continuous delivery
Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...
Agile and semat v0.91
Agile and semat v0.91
Agile concepts for quality and process engineers for slideshare
What is agile model?Working of agile model
Continuous Delivery: why ? where to start ? how to scale ?
DevOps Workshops Fall 2016
Devops Mindset Essentials
Computing DevOp Summit
Continuous Delivery
Fundamentals of Agile
A Software Engineer
Should i break it?
Lean and Kanban-based Software Development
Lean & Agile Value Streams
Lean UX in an Agency Environment
Are you Agile enough?
Ad

Recently uploaded (20)

PPTX
Agentic AI : A Practical Guide. Undersating, Implementing and Scaling Autono...
PDF
T3DD25 TYPO3 Content Blocks - Deep Dive by André Kraus
PDF
Adobe Premiere Pro 2025 (v24.5.0.057) Crack free
PPTX
VVF-Customer-Presentation2025-Ver1.9.pptx
PDF
Softaken Excel to vCard Converter Software.pdf
PDF
Which alternative to Crystal Reports is best for small or large businesses.pdf
PPTX
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
PDF
Odoo Companies in India – Driving Business Transformation.pdf
PPTX
Operating system designcfffgfgggggggvggggggggg
PDF
Understanding Forklifts - TECH EHS Solution
PDF
Claude Code: Everyone is a 10x Developer - A Comprehensive AI-Powered CLI Tool
PDF
wealthsignaloriginal-com-DS-text-... (1).pdf
PPTX
ai tools demonstartion for schools and inter college
PDF
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
PPTX
Transform Your Business with a Software ERP System
PDF
Design an Analysis of Algorithms I-SECS-1021-03
PDF
System and Network Administration Chapter 2
PDF
2025 Textile ERP Trends: SAP, Odoo & Oracle
PDF
AI in Product Development-omnex systems
PDF
Wondershare Filmora 15 Crack With Activation Key [2025
Agentic AI : A Practical Guide. Undersating, Implementing and Scaling Autono...
T3DD25 TYPO3 Content Blocks - Deep Dive by André Kraus
Adobe Premiere Pro 2025 (v24.5.0.057) Crack free
VVF-Customer-Presentation2025-Ver1.9.pptx
Softaken Excel to vCard Converter Software.pdf
Which alternative to Crystal Reports is best for small or large businesses.pdf
Agentic AI Use Case- Contract Lifecycle Management (CLM).pptx
Odoo Companies in India – Driving Business Transformation.pdf
Operating system designcfffgfgggggggvggggggggg
Understanding Forklifts - TECH EHS Solution
Claude Code: Everyone is a 10x Developer - A Comprehensive AI-Powered CLI Tool
wealthsignaloriginal-com-DS-text-... (1).pdf
ai tools demonstartion for schools and inter college
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
Transform Your Business with a Software ERP System
Design an Analysis of Algorithms I-SECS-1021-03
System and Network Administration Chapter 2
2025 Textile ERP Trends: SAP, Odoo & Oracle
AI in Product Development-omnex systems
Wondershare Filmora 15 Crack With Activation Key [2025

Design without Designer

  • 1. » Design Without Designer
  • 2. Avoid Patterns which make your system Monolithic Modularity through •Distributed/out Process components •Self hosted Services/Components Products not Programs/Projects Decentralized Governance Design Should Evolve Infrastructure/Software delivery Automation
  • 3. » World has always been changing, evolving in manner that it has amazed a common man in all walks of life. “Change” followed by “adopt to change” are the key, that made humans innovative and showed the path to evolve. The “guru mantra” worked in all eras, be it a “stone age” or the world of 21st century. This is well received in personal life, business or education and research or any other avenues. Those who perceive the change, make adjustments to the change "early" are the winners in their area
  • 5. » Promote variation, experimentation, trying new things. Let not fear of failure stops your innovation. » Embrace change, design for change » Natural Selection => Accountability » Feedback- Embrace and adopt what worked, leave and quit what not worked. (Failures are feedback only) » Evolve Design, instead of spending a lot upfront, Less Design/Architecture, more Implementation. » Develop in-house capabilities on core components and outsource only commodity Products . As its easy, fast and cheaper to experiment and evolve on in- house as compare to Vendors » Quick plan/analyses/design, experimentation, implementation , accountability and repeat the cycle is the new world order of software delivery
  • 6. » Main points: ˃ Avoid patterns which make your system monolithic ˃ Modularity through distributed processes/components and self-hosted services/components ˃ Products, not programs/projects ˃ Decentralized governance ˃ Design should evolve ˃ Infrastructure/software delivery automation » De-coupled, modular design ˃ Favor micro services that perform one type of functionality ˃ Evolve and scale services as needed rather than more instances of the same large application ˃ Make components containerizable – allows greatest flexibility as far as deployments go » Emphasis should be on products, not programs or projects » Design should evolve as needed ˃ Things should be designed so that they are flexible – requirements will change, so design will need to follow ˃ Allow for …????? ˃ Promote variation and experimentation. ˃ Fail fast and pivot – if something works, keep it or make it better. If it doesn’t, make it so it does or get rid of it ˃ Don’t be married to code. Not all code works ˃ More time spent implementing, less time spent designing. Make the design a good starting point, and change things as needed » Software/delivery automation ˃ Need to have the deployment pipeline as automated as possible to allow for quick evolution ˃ Continuous integration and push-button deployments if possible » Infrastructure considerations ˃ Make it as easy as possible to deploy new resources + Containerization, all dev dependencies like Frameworks, runtimes. Abstraction over OS ˃ Consider cloud computing + Already virtualized, very scalable, easy to set up new instances