Most of the technical organizations today have a simple problem how do we deliver value to the end customer using technology in the cheapest and quickest possible method. The software industry is at a stage where we have become fairly good at delivering any requirements explicitly stated however to discover requirements that are not explicitly stated we have struggled with it for more than 3 decades.  I keep hearing this when I talk to senior technology experts. we don't have domain expertise what can we do? We know only technology hence we cannot drive the customer's business.  "We deliver what the customer ask to deliver"  There are certain methods that can be learned and certain mindsets which can be developed with practice do help one become a Technopreneur.  Technopreneur is precisely a person who can actually go to the customer, tell them this is your hidden/unstated need, that you did not know you wanted. Then deliver it in the cheapest and the shortest time possible causing delight. In this episode of Saturday Architecture, we discuss some of

This week we had a festival called Bhoghi in southern part of India. an important ritual as a part of this festival is to collect the waste from your house and burn it. it is an interesting ritual as we identify things which are hampering our quality of life and removing them and making a clean start.

As I was thinking about this it occurred to me from years ago when I had learned about lean manufacturing while reading the book “Toyota Way” it talks about 7 types of waste

1. Transportation

2. Inventory

3. Motion

4. Waiting

5. Overprocessing

6. Overproduction

7. Defects

This set me thinking as an architect -

“What are the wastes I could remove from the systems which I am responsible for as an architect?”

“removing an emerged guitar branches” , “unused reports and unnecessary data jobs running in production“, many more…

Great Resignation  

Can architects stem the flow? Yes seems to be resounding in answer 

A few pointers 

• Making the CEO or the CTO look good 

 • Providing a technology vision helps 

• Ensuring impact of the team’s work

 • Making architecture look sexy  

#greatresignation #architects

#log4jvulnerability has created havoc. I escaped this time but note sure about next time.

The architecture will fail. Solutions will fail. How to handle them cleanly.

As an architect, I used to think/say  

How can it be my responsibility alone to develop a good architecture? Some challenges insights.

For new business solutions, when the customers  are unknown. 

In this scenario how to develop applications to meet unknown expectations?

SatArch Ep- 53 :

After 28 years I realized there are many customers who I DONT care about?

Deepak - Someone who pays is the customer they are not end-users 

Venkat - The development team is also customers. Why do we need to think like this?

Nishanth - The end users are only high-value customers. Giving the right value to customers. What is the right value?

Kumaran - The operations teams are the most ignored, customers. They are most resistant, but why?

What is #customerexperience  (CX)? It is a big intangible. Interesting insights in less than 3 minutes

Deepak Sharma- The difference between CX, UX, and UI

Sidambara Raja Krishnaraj – Using job theory and Co-creation as a CX levers

Venkatesan Oosur Vinayagam - Managing changing needs is CX

Nishanth K Pillai -  Making a promise and keeping it

Venkataraman Subramanian you passion.

Some questions

This is not an easy question to answer. It depends on the context and the scope of the architect's responsibility also. Let us look deeper into what are the other parameters which determine what the responsibility of the architect is with respect to new technology adoption either by the technical team or by the business.