Saturday Architecture

Saturday Architecture

By Tiny MagiqTechnology
Download on the App Store

Saturday Architecture episodes

  • What do I with AI immediately in my team ?- SA- 71

    Are you tired of doing all the work yourself? Want to sit back and let a robot do it for you? Well, you're in luck! In this article, we'll explore how to use AI to become the ultimate lazy person. Just kidding, we'll also discuss its benefits for productivity and innovation.
    Artificial intelligence and its tools and applications have really taken off in the past 6 months. To be exact the ability to use AI has come closer to the normal person beyond data scientists. When I see the normal person I mean architects, project managers, developers, operation leads, etc. So this episode is about what are the use cases of some of the leaders that we have decided to implement in the coming 2 to 3 months.

    8 min
  • Architect as a Decision Maker: To Solo or To Consensus Build?- SA- 70

    Solo vs. Consensus Decision Making: The discussion starts with the debate on whether architects should be solo decision makers or consensus builders.  Experience is Key: The speaker shares their experience with a new program manager who changed the deployment schedule and how it unexpectedly led to increased productivity.  To Solo or Not to Solo: The speaker points out that the decision to go solo or seek consensus depends on the size and context of the decision and the experience of the decision maker.  A Dilemma Wrapped in a Mystery: The speaker ultimately concludes that leaders should make conscious decisions with the help of their team, taking ownership of the outcome, whether it's a success or a failure. It's not a "romantic idea of leadership," but a basic quality of a team leader. Or, as they put it, "It's not something extraordinary, just the basic quality of a team leader...unless you're leading a group of ghosts, then it's a different story."

    10 min
  • How do we motivate or inspire them to use it? - Part 4 of 4 Part Series SA- 69

    To motivate users to adopt and use applications, it is important to make the application solve their day-to-day issues or their job, empower them to solve their own problems and involve them in the process of generating and visualizing the idea for the application. Change management and adoption building should begin at the beginning of the development process. It may be challenging to motivate experienced senior executives, but building a sense of community and creating incentives can be effective strategies.

    11 min
  • Why Should They Use Our App/Feature? - Part 3 of 4 Part Series SA- 68

    One of the key challenges, let's assume we develop an application and it is done. The key question is why should the internal users actually use it. Only if that question is answered in their minds very clearly, they're going to use the application.  To inspire users to use it the following are some interesting insights 

    varadharajan srinivasan says -  For me to explain the problem, I have to be in the right context of explaining the problem that they see as a problem. ? Are you in the right context of understanding the problem?    

    Deepak Sharma says-  If you are able to connect to the scenario of the end user, the context. "Walking the Gemba" from lean, which is you are in the situation with that user and experiencing what they are actually experiencing in the day-to-day. Explain the developed feature contributes to the solution of that scenario only then the solution would make sense to them.

    Sidambara Raja Krishnaraj says -   To get the scenario right two popular tools help immensely.  One is "Jobs to be done" and the other is  "Value stream mapping".  Also eliciting the "what is in it for me" for the user we're trying to provide. Using cocreating with the users to build a vision for the future for the solution and upcoming features. Prepare them well ahead before release.


    Kumaran Anandan  says-   The insights shared by leader Nagaraja Srivatsan in how a Wall Street Journal article on adopting AI in retail and its relevance in healthcare and AI.   Appeal to the user's identity and purpose as a person  Every individual wants to be a better version of themselves. So this person sitting as a data entry person, you'd say you can be a much kinder, nice, caring person by making sure that you enter the data correctly. Because if you enter the data wrong, somebody's health will be affected.  Convey to them - "You are a protector of somebody's health. Now to protect that person. This feature will help you."  Finally, the context is about the user and not the feature.

    9 min
  • Who exactly is the customer? - 2 of 4 Part Series SA- 67

    Are we dealing with the right customer?


    There are two types of customers we deal with from an IT perspective. First, there is a direct customer which can be the HR department or the finance department, then there is the indirect customer of the HR department and the finance department which could be the employees who are the external vendors.

    The customers could also be classified into 3 broad categories: Providers, Consumers, and Aggregators. The Providers are teams that provide services like network, storage, data center operators, etc. The Consumers are departments like HR, finance, etc. The Aggregators are developers who actually make the application.

    The regulators are good examples of these types: security team, procurement team etcetera

    But they're not all created equal! A good example of this is when you're looking at a "Sponsor" type persona; a sponsor is a person who can state what is the business value of using this application and its relevance to organizational success.

    13 min
  • Internal customers are tough - 1 of 4 Part Series SA- 66

    I have developed an application for my corporate users, basically internal employees. This was done with a lot of sincerity, business study, and getting buy-in from them. but after the system goes live no one seems to be interested in using the application however hard I try, which is very baffling and irrational. After all, I made this application based on the end users request and did a study with them. 

    Why will they not use it?

    7 min
  • Whose neck should be on the line? SA-65

    Who is responsible for the ultimate success of a business aka Revenue/Profits? This becomes an even tougher question in today's world when everything is driven by technology. For a technology company, this becomes even more critical.

    54 min
  • Does the architect's job change in a hybrid scenario? SA-64

    The architect and the architecture team will have different responsibilities in a remote working environment.  \

    One of the most confusing aspects of hybrid working environments is that there are no formalized guidelines to set standards. That means that every team will be different. 

    When it comes to architecture and development teams working in hybrid environments, there tends to be a split of opinions. Some say you should continue on the same path you had before and others believe the best way forward is to change things up a bit.

    18 min
  • Local Vs Global Best Practices SA-63

    Dont follow Global "Best Practices".


    Are Global Best Practices Bad?

    The answer is yes, and no.

    It depends on what you mean by “global best practices” and how you use them. If you're looking for a way to implement a global concept or process in your organization, then the answer is probably not: global best practices can be a dangerous distraction from actually innovating and building your own local practice. But if you're just looking for ideas that have worked elsewhere, then they can be very helpful!

    We will be discussing this topic with Deepak, who has worked in both Asia and America. He's also an expert on cultural differences between Asian countries as well as between American companies. In this conversation, we'll look at some of the different ways that we can use global practices effectively in our own organizations—and how we might need to change them when they don't work as well in our context.

    13 min

About Saturday Architecture

From the publisher's feed

Let us begin a weekend on a strong note. Saturday we discuss topic on architecture and we talk about experiences not theory.