How We Work

The Brick Abode Way

Discover how we work and our process in detail.

The Brick Abode Way keeps us proactive and driving improvements, in addition to executing. Every team at Brick Abode works this way. We train all of our people how to do it well. Our leadership team performs continual quality control on it, from daily status checks to presence in the weekly meetings to our deep-dive quarterly reviews. Because it allows us to be consistent, the simplicity of the model is one of its greatest strengths.

It gives our management team tools to ensure that Brick Abode is being proactive and effective for each one of our clients. The consistency of our execution is what makes it work.

  1. Daily status updates
  2. from each team member. These are posted in the messaging forum (Slack and whatnot) we share with our clients. They come at Start-of-Day (SOD), End-of-Day (EOD), or both. They create visibility for what the team is working on.


  3. Weekly written reports
  4. explaining the work done the previous week, any problems or mistakes we found, suggestions for improvement, and the priorities for the coming week. It also has meticulous records of tickets worked and timekeeping. This is accompanied by the next item…


  5. Weekly meeting
  6. with the client, the most important step. We go through the report, discuss problems/mistakes/suggestions, and review priorities and plans for the next week. We update the report based on client feedback and re-issue it as necessary. We ask if our reporting and meeting structure is working, addressing the issues that are important to the client. Every weekly meeting includes the Team Lead, usually all of the developers, and at least one member of Brick Abode’s leadership team.


  7. Quarterly review
  8. to look for opportunities we might be missing, drive proactive suggestion-making, and perform quality control on our work. This is especially important in devops, where you need to take special care that you are not overlooking necessary work, but we apply it to all teams. Sometimes our clients are not interested in participating, in which case we still perform the review internally, with our entire management team spending several hours with the Team Lead doing a deep-dive on the previous quarter.


Background Image

Our service design

The model drives good relationships with clients:

  1. Our clients are as informed as they want to be.
  2. When they have to ask us for clarification or more information, it is the exception, not the rule. As one of our clients once said to me, “I would not say that Brick Abode communicates too much, but I would say that you come close.” Our standard reports are detailed, and we customize each client’s report based on their feedback to give them exactly the information they want and need.


  3. Our clients can understand and direct our work easily.
  4. Clients know what we have been working on, and they know what our plans are. If the client is busy with other tasks and wishes for the work to continue in the previously agreed direction, then they have confidence that it will happen. On the other hand, if changes need to happen, then those decisions can be made immediately. Their control over our work is absolute and effortless.


  5. Our clients know about our mistakes and work with us to improve system safety.
  6. Thanks to our no-blame culture, we always self-disclose our mistakes. By acknowledging that individual errors are inevitable, the company as a whole takes responsibility for errors instead of blaming the individual. We focus on identifying and rectifying the causes of errors, and proactively improve our safety measures to prevent accidents before they happen. Each mistake is accompanied by an analysis of why it happened and a proposal to fix the underlying problem. Finally, we decide the path forward together with the client.


  7. We’re not just ticket-closers; we’re problem solvers.
  8. In addition to executing our assignments, we are constantly looking for ways to improve the effectiveness of our work and actively proposing how to do so. This takes many forms: discussing whether the current investment in automated testing is the right business decision, driving continual improvement in the CI/CD/release pipeline, cooperating with devops to reduce operating costs and failures, suggesting architectural improvements, bringing outside innovation to our problem solving… the list goes on. The point is that we view it as our responsibility to find and propose these things, not leave the entire burden with the client. We want our clients focused on growing their business, so we try to drive as much improvement as we can ourselves.

    A major mistake of traditional outsourcing is to view their job as merely executing assignments. Our goal is to understand and help solve your technology problems; executing assignments is simply one of the ways that we do that. Creating a pleasant experience, letting the client direct our work effectively, driving improvements daily, and removing as much burden as possible from the client are critical elements of our success. Helping our teams achieve this is the most important job which our leadership team has.


LOREM IPSUM DOLOR 2019

Lorem ipsum dolor sit amet

Article Image

Lorem ipsum

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.