CET Extension Design
CET has become the industry standard design tool in North America. The ease of using CET allows the user to quickly draw, specify, and render spaces. The major manufacturers invested early and built their product catalogs. Open line manufacturers have heard the comments from designers “if you are not in CET, your product will not be specified”. It is now the race to build a CET extension.
Before you can build, do you have a plan? Are you relying on others to make decisions for you about your extension? Did you know that if your extension is not user friendly, it is unloaded and never used again.
I actively participate on the team to help build the blueprint for the extension. User needs, your product unique qualities, and CET best practices are delivered in the end product. You are provided the information to make informed decisions about the investment in a CET extension. You don’t have to be a CET expert, just partner with the expert teams.
Design Process
KICK-OFF MEETING
Together with the development partner, the scope, schedule, and goals are identified.
Reviewing the primary components of a CET extension demonstrates how your product can be represented.
The components identify what users expect and provide consistent experiences across all CET extensions.
Prototype
Before your extension is built, previewing a prototype allows you to approve and adjust before it is built.
User testing and feedback sessions are completed to learn more from the user community. Incorporating the learning and changes early in the process will save time and money on the total project.
STAND-UP MEETINGS
Participating in stand-up meetings, includes the development team, extension manager and UX&Kari. The meeting provides a forum to discuss what everyone is doing, completed, and blockers.
Virtually the team creates a consistent cadence for decision making and tracking progress. UX&Kari ensures the development process aligns with the product capabilities and the users needs.
BETA TESTING
A final review before the extension is released on the marketplace. The extension is available is as a beta, only accessible to assigned users. UX&Kari completes a thorough audit based upon a 100+ point inspection list (created by UX&Kari). Because the team has been working closely together, minimal changes should appear.
It is suggested to create a user beta team to include testing feedback. UX&Kari facilitates the testing, findings, and recommendations to the team.
Configura also completes a QA Review before the extension is released in the marketplacce. All of these checkpoints are considered during the development process. When the process is followed, minimal red flags should appear on the QA Review report.
COntinuous improvement
Releasing an extension is not a check the box and done. Remaining relevant in the everchanging technology space requires the extension owner to be engaged.
TechBox Collective provides an online community space for extension owners to stay informed about CET extensions and the e-tools you are invested in.
NAVIGATING through e-tools
It can be overwhelming. UX&Kari provides you the 1:1 attention to answer your questions, prompt you to what is next, and introduce you to others that may be able to assist you.