Placeholder for the image "https://storage.googleapis.com/scm-seeed-prod-bucket-33dc43aaefd74208/pexels_kevin_ku_577585_8bdc4b7fe5/pexels_kevin_ku_577585_8bdc4b7fe5.jpg".Seeed’s method: Continuous Improvement and Continuous Development

Seeed’s method: Continuous Improvement and Continuous Development

Continuous Improvement and Continuous Development means keep improving and keep applying those improvements. There are several reasons to do this in any business. Let us give you a real-life example such as APPs because creating software is exactly like any manufacturing process, so let's get into it

Rowland Saer

Rowland Saer

May 18, 2021

4 min read

Seeed’s method: Continuous Improvement and Continuous Development 

We "keep it simple for the customer" and that’s our philosophy. The actual process is called continuous integration and continuous delivery. However, this process is highly technical and challenging to understand, but instead of getting all technical, we can add some seasoning and apply it to everything.

Why? Because we really need to.

This is something that will change your business forever. Continuous Improvement and Continuous Development means keep improving and keep applying those improvements. There are several reasons to do this in any business. Let us give you a real-life example such as APPs because creating software is exactly like any manufacturing process, so let's get into it.

If you want to build an APP, where do you start? Let's make a list (this is going to be fun because most people don't think that APPs are that complicated).

Let's say that we are going to build the Instagram App, so on the user side we need an APP that you can install on a mobile phone plus:

  • A login system
  • A user management system
  • A database to privately store user data and pictures (for internal messaging)
  • A database to publicly store usernames, tags, pics, and comments
  • A feed so the user can see other users feeds
  • Ability to post pictures 
  • Ability to add text
  • Ability to like pics
  • Ability to comment on other users pics
  • Ability to tag other users etc.

Plus, it would help if you had a master APP o to manage, monitor, block, or ban users from the platform.

And the list goes on because building things is a complex task, so you need to be as accurate as possible and as practical as possible, but the most important thing is that you need to plan it right; otherwise, you'll run into more and more issues later.

Continuous improvement means that even from the planning level, you are looking for the best options, parts, and processes to build that APP, so it's not only about performance, looks, or popularity. It's about the future.

For example, when Instagram started, you couldn't tag people or send direct messages. Those features were added later as part of the continuous improvement process, and probably they knew they needed them, but they prioritized the most important ones first.

This is a key part of our process, and it should be a part of yours too. Why? 

Because it saves money, it saves a ton of money…

And the reason is straightforward, and if you know what you are going to do next, you can prepare your product, APP, or project to handle it. This also means that it's part of the planning, so it also means less planning from the super expensive time of the management team.

Let me give you an example using the same Instagram APP. If you add internal messaging to the initial "dream features," we can prepare the database to hold two. Also, we can leave room in the user account to manage and view the messages, and we can prepare for it.

But if you ask for the same feature once the app is ready, it's a completely different story. First, we need to evaluate the requirements, analyze the infrastructure, run some tests, evaluate compatibility, add all the variables to the code, new databases, permissions, etc.

And you can save all that time just by planning it. The same goes for new features out of the blue; you add them to the dream feature lists, finish the old ones thinking about the next ones on the list, and add them while preparing the platform.

That's why for us, this is the only way we can focus on the whole project, planning only once or twice a year instead of doing it with every feature, set realistic delivery dates, and keep improving and keep developing.

This way, your app is always up to date, always evolving, and never obsolete.