Free Webinar Series : CTO Accelerator- Register Today!
AKF Partners Logo Technology ConsultingScalability - We wrote the book on it ℠

AKF Blog

Scalability and Technology Consulting Advice for SaaS and Technology Companies

Safely Paying Down Technical Debt for CIOs

This post helps CIOs quickly assess where technical debt occurs throughout the organization to identify short term and long term investments with the right owners. We’ll focus in more detail how to address the debt that accumulates when a core operating platform such as an ERP has failed to keep up with the needs of the business. This debt is typically a combination of inefficient tools being maintained by technology department, inefficient workers (labor) in the business using various tools to manage various processes, and lost business opportunities (revenue) from a workforce that can’t compete as quickly as its competitors. To unwind this mess, CIOs need to map the current systems (tools) they have built and map the current processes (people plus tools) as they exist in the organization. By analyzing the combination of tools, processes, and people, it becomes much easier to identify short term and long term solutions. This also greatly reduces the risk of a long term solution such as an ERP replacement.

Phillip Seawright

· 6 min read

Reduce DNS lookups to improve website performance (Rule 4)

Believe it or not, website speed is directly related to conversion and revenue. One element that delays the time before a user can interact with a website is DNS lookups. In this article I’ll talk about how to reduce DNS lookups for your website.

Curtis Nielsen

· 4 min read

Architectural Principles: Build vs. Buy

In many of our technical due diligence engagements, it is common to find that companies are building tools with considerable development effort (and ongoing maintenance) for something…

Pete Ferguson

· 5 min read

Technical Debt for CIOs Leads to Organizational Debt for CEOs

Enterprise software used by B2B and B2C companies is an expensive tool designed to help the workforce be more productive. This expensive tool is an asset that needs to be maintained. When organizations fail to maintain their expensive tools, the workforce is required to use less efficient tools to get the job done. When you incur technical debt as a buyer or renter of enterprise software, it shows up as organizational inefficiences with longer cycle times, more errors, and increased risk of adverse events.

Phillip Seawright

· 3 min read

Key skills for adaptive product teams

There is growing recognition for the need for adaptive product teams.. The process of delivering software may be very similar across almost all companies but there is a need for…

Tanya Cordrey

· 6 min read

Scalability Rules - How to Simplify Scope, Design, and Implementation (Rule 3)

Scalability Rules - How to Simplify Scope, Design, and Implementation (Rule 3)

AKF

· 9 min read

Architectural Principles: Scale Out, Not Up

Plan for success and design your systems to scale out. Don’t get caught in the trap of expecting to scale up only to find out that you’ve run out of faster and larger systems to purchase, lease, or rent.

Pete Ferguson

· 3 min read

Microservice Aggregator Pattern

When and how to use the microservice aggregator pattern

Marty Abbott

· 4 min read

Working from Home, Is your Business COVID-19 Ready?

Applying proprietary AKF Models determines if current or future architecture can handle scale. These models help deal with some of the current uncertainty and withstanding higher levels of demand.

AKF

· 3 min read

The DID Process - Scale Design Principles (Rule 2)

When do I scale my company? Use The DID process to scale efficiently at the right time.

AKF

· 10 min read

Why Code Reviews Save Money and Time

Code reviews increase quality and should not affect time to market if implemented correctly in addition to providing greater learning and collaboration between peer Engineers.

Pete Ferguson

· 3 min read

Ambassador Pattern: Description and Advice on Usage

How to use and when to avoid the Ambassador Pattern for microservices.

Marty Abbott

· 6 min read

Adaptive product teams: Beware the one-size- fits-all approach

Image Credit: AzoraArashi Flckr‘As such, there is no one-size-fits-all approach that anyone can offer you. The hot water that softens a carrot will harden an egg’, – Clay…

Tanya Cordrey

· 5 min read

Faster Time to Market – How to Avoid Overengineering (Rule 1)

Faster Time to Market – How to Avoid Overengineering [YAGNI] (Rule 1)

AKF

· 9 min read

Contact Us

Categories

Most Popular