5. The main goal of this redesign was to show in a more accurate
way all the contents (more than 200 sections), so the users
could find them easier. Manage usability standars and
accesibility at a medium level.
Designing Process:
Architecture of information: 2 months of sessions with
Stakeholders and a group of users (workers of the organisation)
to determine the communication needs, final site map and the
goals of this.
Interaction design: Planning meetings to determine the
components of each section and how they should work.
High fidelity wireframes
Technical document for developers
Specifications on how the CMS should work for a complete
administration of the site information. Designing the user
experience for the backend.
DOCUMENTATION
Website
6. GRAPHICELEMENTS
Drop down menu with clear
view of the section and its
elements. Sections defined
by color through the whole
site.
Lists of elements to show information through anchors. Reduce
the number of new pages. Integrated content to keep unique
URLs
Use of tabs and alphabet to organice big data
Interative maps
8. Develop a B2B channel for the distribution area so the business
could increase their sales by a better experience (online) and get
new clientes (through the knowledge of their product offer).
The big challenge: use Magento Framework and adapt the data base
model and buying process, to fit the information model in the ERP
system.
Designing Process:
Architecture of information: Redefining the buying process through
an ERP integration: Categories, products, price rules, users
information (new tables in the data base model)
Interaction design:
User stories, use cases and integration flows
Planning meetings to determine the components of each section and
how they should work.
High fidelity wireframes and Technical document for developers
Specifications on how the CMS should work for a complete
administration of the site information. Designing the user experience
for the backend.
DOCUMENTATION
Website
9. E-COMMERCEELEMENTS
Dropdown menus for categories navigation
Carrousel and tabs to promote categories and
products Defining templates for content pages
12. Product architecture for a distribution channel for an electrical
material company in Colombia. Online store for distributors and final
users
Designing Process:
Architecture of information:
Research on the brands that were going to be sold. Understanding
the products and how they are sold. Meetings with product managers
and IT team. Previous attemps for the project and competition
channels.
Defining categories and products (grouped products, price rules).
Taxes and transportation fees for diferent countries.
Interaction design:
User stories and use cases.
Planning meetings to determine the components of each section and
how they should work.
High fidelity wireframes and Technical document for developers
Specifications on how the CMS should work for a complete
administration of the site information. Designing the user experience
for the backend.
INVESTIGATION
14. Product architecture for university in Ecuador. The challenge: make
seven (7) different portals look as one, still keeping their identity and
using a defined number of site templates for almost 500 pages.
Designing Process:
Architecture of information:
Sitemap organization
Content definition ---> templates definition
Defining blocks and its uses for Drupal developers
Interaction design:
Planning meetings to determine the components of each template
and how they should work.
High fidelity wireframes
DOCUMENTATION
15. Business consultancy and Product Architecture for Sueños
Cumplidos, an online platform to help people build and conquer their
dreams, based on incentives by other users and brands.
E-commerce and Addsense for companies.
Building the business through the product: Defining objetives of
the product and strategy for final users and companies to be
involved. Metrics and revenue model.
Designing Process:
Architecture of information: User stories for final users, companies
and admins. Work flows and use cases.
Interaction design:
High fidelity wireframes for each work flow with comments for
developers (backend and frontend) and administration.
Technical document for developers
DOCUMENTATION
17. Designing an interactive kit for cars insurance users, as part of a
complete portafolio of interative kits for all kind of insurances.
Designing Process:
Architecture of information: Defining content and its priority
Interaction design:
High fidelity wireframes and prototyping
PROTOTYPE
