Douglas Information Systems Corporation

Disciplined Solutions Architecture

Focusing on customer need, we work with customers to successfully create solutions for the enterprise. Architecture is one of the most important steps early on and throughout the project lifecycle. We ensure everything fits together optimally and guide successful execution while ensuring technical and business buy-in. Trade-offs and decisions are documented with stakeholder buy-in while ensuring all stakeholders are on-board with the solution. Business conflict between teams and different agendas is mitigated through understanding and communication and ultimately the organization is lead to a highly capable and optimal solution. We take into account all required facets from the enterprise, including business requirements, non-functional requirements, IT security, legal and regulatory, governance, GDPR/PIPEDA, etc.

Software Architecture and Software Development Leadership

We have an expert level of experience designing and architecting large scalable enterprise software applications ($15M/y; 70+ team members in-flight) and providing software development leadership to small and large teams. We work with our customers and do whatever it takes to successfully bring web, mobile, and enterprise software to the market.

Our 10X Rule

We are not worthy to our customers unless we are providing a minimum of 10x returned value.

Tracking and KPIs

We are so confident in the value of our services that we will work with our customers and implement measurable KPIs where necessary to ensure our customers are confident with every milestone we make every step of the way.

Our Customers

Our customers include new startups as well as top enterprises in banking, insurance, manufacturing, healthcare, public relations, and technology. Some of our customers include Microsoft, Avanade (Infusion Development), The Great-West Life Assurance Company, Manulife Financial, Blue Sands Inc, PC Shop Inc, Blueprint Systems, and GlobeNewswire (MarketWired).

Dan On Software

Clearing up Disaster Recovery and Business Continuity Confusion

As I work with different teams, there is often some confusion about what people mean when they say “DR”. Team discussions will delve into RPO, RTO, Backup, High Availability, and Business Continuity. Unfortunately, these concepts get mixed up and confused […]

Daniel Douglas

Using Kevin O’Leary’s Advice on Deal Making Inside the Organization

Staunch American capitalist Kevin O’Leary once said, “the very best deals are when you feel you left something on the table, and the other side feels the same way”. He made this statement back in 2020, and it has stayed […]

Daniel Douglas

Setting Yourself Up to Become a Solution Architect

There are a few different path’s I’ve seen people take to grow into architecture roles, and many people will grow into an architect role from more senior technical SME roles (senior developer, development leader, infrastructure leader, etc). It’s not always […]

Daniel Douglas

Evaluating Solution Architect Competence – 10 Indicators

For solution architects to be effective and to succeed there are specific competencies that are crucial. These competencies become even more crucial as architects evolve from technical roles to solution architect, senior solution architect, and principal architect. Perhaps you are […]

Daniel Douglas

Bad Security Practices Pushing the Citizenry into the Arms of Bad Actors (GC)

Over the last few weeks, my wife and I have been helping complete a Canadian tourist visa application for a family member. It’s long and it’s tedious but we expected that. We get to a point in the application process […]

Daniel Douglas

The Project Manager and Solution Architect Relationship

Solution Architects and Project Managers work together and require good dynamics in order to be effective. There is no subordination in this relationship and the roles are complementary to each other. I’ve seen good dynamics, but I’ve also seen toxic […]

Daniel Douglas

CQRS Performance Design Pattern Demystified

The command and query responsibility segregation (CQRS) pattern is a pattern that can be deployed as part of microservices and other architectures. This pattern is often overlooked by architects and development teams even though it is a well documented pattern. Even […]

Daniel Douglas

Challenging previously held beliefs and moving forward with architectural “anti-patterns” in the enterprise

Nobody claims to like anti-patterns, and I certainly don’t like them. In fact, when it comes to architecture and solutioning, we identify them, make sure we understand why they are bad, and then we avoid them. We help others to […]

Daniel Douglas

The Journey. A Story About Turning Business Requirements Into Solution Architecture.

In a previous article titled A Methodology for a Transparent and Traceable Solution Architecture, I outlined a methodology an architect can use to create a transparent and traceable solution architecture. This article will expand on that and will use a […]

Daniel Douglas

A Methodology for a Transparent and Traceable Solution Architecture

As a Solution Architect, you intersect with all entities that have a vested interest in the solution, including, business sponsors and associated business team, business managers, and business analysts to different degrees. As being responsible and accountable to get the […]

Daniel Douglas