Rahul Saxena - How Design Thinking created WOW factor in Peer Review?
What is the background situation/context for your probe?
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.
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.
What is (or has been) your hypothesis?
When seen from the lens of another agile approach, it's evident that feasible results are obtained when customer trust is there in knowing that you have identified his/her problem statement and he/she is part of all the stages of SDLC and not kept isolated.With the above background its clear that we were in greenfield project approach where nothing was known to us about the product hence, it was important to select some approach to start of with and involve end user in every step to understand and learn the where about's as and when we progress.
I propose using the ‘Cognitive approach - Design thinking ’ which aligns the customer requirements and also makes you not only empathize with your end users but ideate with them and showcase them with something tangible early in the period and get continous feedback and thus creating the "WoW" factor.
What is the experiment you would like to run (or you have run) and how can this experiment validate or invalidate your hypothesis?
To validate this hypothesis, we kicked off with cognitive approach i.e. design thinking by bringing every singe stakeholder from end user to technical architect to developers in one room for two weeks and conducted a workshop and post which we had something to know about the problem statement and MVP and then we met once every sprint to get regular feedback and keep showing our progress thus resulting out giving the end users with MVP product to kick off their tasks in six months.
Is there a specific skill/technique you would like to learn/explore at this coach camp?
Ways how other organisations are working on making themselves involved more with their end user and creating a "WOW" factor for them and hence creating a culture of learning and innovation.Would like to understand how they are able to sustain on the actions they are taking.
As change agents/coaches, we are also impacted, hence how can we make sure that teams are getting the environment and transparency and courage to be visible to their end users and working with them.
Call for Papers CLOSED
Ended on Jan 25 '20 05:29 AM IST
Interested in attending the Agile Coach Camp on Oct 11th in Bengaluru? Read on...
It's been 12 Years and almost 110 viral Agile Coach Camps since our very first coach camp experiment. This year, Coach Camp co-creator Naresh Jain along with Jutta Eckstein and John Buck will lead participants in this Coach Camp in Bangalore, organized as part of the Agile India 2020 Conference.
Coach Camp Theme
As a coach, you're often the one who needs to drive and sustain change. Yet, how do you do this? What has helped and hindered you doing so and how can you best pass your experience on to other coaches or how can you best learn from other coaches?
This is the theme for this year's coach camp. To tackle this challenge, we invite you to try something new:
- Currently, we face the following situation: Constantly driving change is getting more and more important for companies to survive in this VUCA world. At the same time, it is (or should be) the core skill of every coach – no matter if you coach individuals, teams, or organisations. However, sometimes it seems every coach has to come up with her own experience on how to drive change successfully.
- Our hypothesis is that for driving change, every coach uses so-called probes, that are defined by small, safe-to-fail experiments based on hypotheses derived from reflection on the current situation as well as on theory. So, probing allows discovering (based on the hypothesis) what's working and what is not through one or several experiments. This allows to make sense of both the current situation but even more important of the situation we are aiming for. And if we create a knowledge base of our collective wisdom on probes we used (or intend to use) we can learn from each other.
- Therefore, as an experiment we want to invite this year's coach camp participants to jointly discover, share, create, improve, and finally publish probes that help(ed) driving and sustaining change. As in a typical coach camp, we will use the Open Space format to explore different topics for driving change and we invite you to use probes to focus the discussions on these different topics. We anticipate as a result that the discovered and created probes will provide a foundation for such a knowledge base.
Registering for the Coach Camp
The coach camp is free of charge (financially) yet, for registration we ask you for the following:
- Please click on the Add Paper button and submit your position paper. In your position paper, you will be asked to share an idea for a probe, consisting of a background situation (context), a hypothesis, and an experiment. This can be a probe you've implemented before, one you've discovered/heard of others implementing it, or you intend to implement. The probe should focus on the coach camp's theme: Driving Change.
- The discussed probes provide a basis for a free and publicly accessible knowledge base.
Please note, we want to invite you to use probes for the discussion and recording of the Open Space sessions. This is by no means an enforcement. We are well aware that there might be situations where probes are not the right means for discussing or/and recording a particular topic - and that is of course fine. After all, using probes for this coach camp is a probe in itself (and we are open to possibly invalidate our hypothesis.)