What is tech intensity?
Malik explains that tech intensity at a company has 3 dimensions:
- The adoption of technology
- The capability of individuals to use the technology
- And trust organizations have in deploying the technology
Each dimension of tech intensity builds upon the others.
Two diagrams, the first is a Venn diagram that explains how tech intensity is the intersection of technology adoption of a company, an individual's capability to use the technology, and organizational trust to deploy the technology. The more those three areas overlap, the higher the tech intensity of a company. The second diagram is a 3-dimensional cross-section of the Venn diagram. It is meant to illustrate that to increase tech intensity, or to increase the overlap between each of the three components, a company must have cross-cutting communications across departments.
"Looking at it from another way", Malik explained, "tech intensity is all about breaking down the silos we work in and enabling cross-team productivity."
Caleb raised his hand, "But here's what I don't get. My team of field technicians can work with Maria's team of inventory specialists to come up with a great way to handle inventory at the warehouse. But without getting Kiana's team of software developer's involved... where does the technology in tech intensity come in?"
Maria almost interrupted Caleb and said "I've been studying up on Power Apps in my spare time. And Power Apps excels at enabling business professionals develop applications that are easy to create and deploy."
"Citizen Developers" observed Kiana. "Business professionals who use their domain knowledge to create applications from the data they already have access to using Power Apps are Citizen Developers."
"And when Citizen Developers are enabled to create apps that exactly suit their needs, my development team can focus on delivering high-value reusable software across the company. That eases our backlog, and the software we create helps provide the data needed by our Citizen Developers."
Preeti couldn't help but smile and say "And Power Apps is all run from our M365 tenant. So it's fully managed from an IT perspective from the start."
Fusion development teams
The team now sees how they can work together to create software:
- Business and IT domain experts from across the company identify and collaborate to find solutions to company-wide problems
- Business owners create Power App applications that exactly address and solve the problem
- The software development team focuses on providing data and complex logic the Power App application can consume
- And IT can easily manage rollout to get the Power Apps into the hands of the users immediately
This shows how the VanArsdel fusion development team is organized. And how each job role previously discussed in the company maps to the role the person plays in a fusion development team. It is driving home the point that business professionals work with technology professionals to build better apps faster. There is also a flowchart on this graphic that indicates the steps of the fusion development process at a high level. The first step is the kick-off, or when a citizen dev identifies a problem and a team forms around how to solve it. The second step is planning to solve the problem, and the third step is execution, or when citizen developers use Power Apps and professional developers use the tools they are comfortable with to build the apps.
Malik smiles and says, "This is a Fusion Development Team. Citizen Developers working with Professional Developers to increase VanArsdel's tech intensity!"
"And", Preeti says, "everybody works with the tools they are already comfortable in. Everybody is more productive because we're not being asked to learn anything completely new."
"Now, what exactly is this Field Inventory Management System we need to figure out?"
Need help? See our troubleshooting guide or provide specific feedback by reporting an issue.