If I had more time, I would have written a shorter letter.
What is the difference between simple and easy? We talk about a journey of an ecommerce product development where as a product team we made a conscious decision to incessantly strive to keep things simple and lean (by default).
I will share examples of product companies that champion the concept of simplicity. Companies like March Tee, Bose, Apple, Google and a few others that are trying hard to keep their product and UX designs simple. Getting inspired, we chose to use the philosophy of “Making it Simple” in building our teams, adopting Agile methodologies, choosing the right set of ceremonies, technical practices, UX design etc. In addition, having the voice of our target users in the development process, helped us build the right MVP and eventually churn out the product that delighted the business and users.
We kept asking the question “how can we make this simpler?” Answering this was important, for each aspect of the website design or the code being written for it.
Outline/Structure of the Talk
- People often confuse and use the words simple and easy interchangeably. I begin by disambiguating that.
- I will explain why it is easy to make things complex, and why people naturally tend to think like that
- I will share examples of companies that champion the concept of simplicity
- I will then share my own experience of introducing simplicity in various areas of agile product development:
- In building teams
- In adopting methodologies and practices
- In selecting tools and processes
- Building something that users will need and love
- Build v/S Buy
- How can we strive to be lean (by default)
- Disambiguate Simple and Easy
- Inspiring people regarding the concept of Simplicity in various areas of software development
- Sharing personal experience on how to build products by keeping processes and thinking clean and simple
Product Managers, Delivery Leads, UX Designers / Researchers, Agile Coaches
schedule Submitted 2 months ago
People who liked this proposal, also liked:
Rahul Saxena - Peer Review by Embracing Design ThinkingRahul SaxenaSr. Business AnalystCapita
schedule 2 months agoSold Out!
Design is a journey of discovery and as rightly said every design is complex but a little thinking added to it could give you happy customer.
Every organization comes across complex problems and with an approach of breaking those complex problems into small chunks and then addressing them one by one is always a go-to approach. In general terms, there ain’t any flaw with this approach infact it has always turned out to be one of the efficient way of tackling the complex problem.
In last few years design thinking technique has gained a lot of interest and implemented across varied project irrespective of the business domains.
Embracing design thinking helps create new products that adapt to changing market conditions. It’s also realistic: All businesses must become more service-oriented and offer a stronger “customer experience.” As the distinction between products and services blurs, so does the distinction between consumer and producer.
One of the complex came on our way too when we were given a task to build “Peer Review Solution” application used for helping editors throughout their journey which begins from finding peer reviewers for the paper/submission they have got for their journals till finally providing the final decision to publish or not to and not to forget the key part of journey of getting and consolidating the reviews received.
This project sounded very easy initially but it was a core customer centric project we ever did and hence meeting their need was the key to success of this project.
This is where Design thinking technique was implemented by us and was made tangible using its five key elements to create an customer centric optimum, high performing application. In this session, we present a case study of this implementation along with our results and learning’s.