Planning an Enterprise Custom Product Designer Implementation

For small shop owners introducing the online product design feature is a simple step by choosing among the applicable tools on the market. You just walk into sites, talk with people, try the software and agree on signing up if it matches your expectations and the printing technology.

For large companies, it does not work like that. Large portals implement various types of non-standard user stories like choosing between various decoration types, having a preliminary registration, offer large number of products and their variations and lots more. Implementing an online design solution for such companies requires a tailored approach and a proper guidance process.

Having over 10 years of experience in working with decoration industry companies, we have adopted an easy process, coined by Spotify once - Think It, Build It, Ship It, Tweak It. The four phases of the project allow us to align it with agile process we use and allow customer to join our team and work out the solution with best cost-effectiveness. This article would give a brief look onto above phases and how they work.


Think It. From the very first contacts with our clients, we thrive to understand what their business is and what problem they are trying to solve with our tool. This comes in a form of company background, desired user stories, problem descriptions and business goals. Once we have defined a set of initial scope that has to be covered, our team comes up with initial demos and prototypes.

Build It. Once signed up, the team now works more closely with the client team to compile a set of custom user stories, test cases for them and respective performance requirements. Each set of this scope is estimated by the team, so that client is always aware on scope and related cost of the project. The team than plans the sprints accordingly and delivers demos regularly to assure the project is on the track and aligned to customer expectations.

Ship It. Closely to project finish, when around 90% of the scope complete, we encourage client to commence internal acceptance testing and alpha test for the users. At this time both our team and client decides when exactly the product should be released and published to the wide audience.

Tweak It. The project itself isn’t finished with the final release. During the support period, the team stays focused for any performance issues, scope gaps and common fixes to be brushed up for the post-release period. At the same time, both client and team continues to work on further updates, dictated by business needs, thus contributing to overall online product designer value for end user.

The above approach, put into Agile/Scrum methodology we use, provides firm results and is always controllable. For a large company to implement the online design and jump into the market, what could be better?

Add comment