Portfolio
Week1
Mon
Tue
Wed
Thu
Fri
Portfolio
Apart from obsessing over little details and giving creative
solutions, at KiwiTech
we have our own
Design Process
Adopting a Design-first approach, we complete the
designs in 4-5 weeks
& deliver a clickable prototype that works as a bird's-eye view of the product to understand the scope
before diving into the Development.
Let's understand the Timeline
Launch call
the 1st 3 days are for
Requirement understanding &
Brainstorming
The very first step we do, is to gather as much knowledge about
the product from
the stakeholders. Kiwi-Team & the client get together on calls to understand the requirements,
brainstorm and produce a cohesive set of requirements at the end of this engagement.
After each call, Kiwi-Team huddles back for an internal
brainstorming session and
narrows down the feature sets. The Gaps or TBD points are taken in the subsequent calls with the
client.
An FRD (Functional Requirement Document) is also being worked on in parallel from where the approved features will be picked up for designs.
We call this 
Starting the
Design sprint
As The week 2 starts
We start working on the
Wireframes
The wireframes help us quickly draw out the screen components & navigation points before we actually get into a detailed branding and styling. With these we are able to finalise the necessary things required to make a final layout.
A Showcase is planned for the
deliverables!
by this week
We also tailor the
Design concept
We experiment with the colors for background, images, typography,
formatting,
icons, navigation styles, CTAs and try to create 1 or more unique concepts carrying the brand’s
look and feel.
A Showcase is planned for the
deliverables!
A Concept is Approved
An actual footage of 2 designers showcasing their concepts to the client.
& sometimes things could get quite dramatic!
Closing this Week!
The clients are able to pick the concept they like or mix 2 concepts and
finalise a layout that is to be taken as the design guide throughout. The wireframes and the
design
concept give client a substantial room to evaluate the progress made so far & anticipate how the
product prototype is going to look like.
A Concept is Approved
Week3
Week4
Week5
The next 3 weeks are
Dedicated towards
Designs
With the requirements, flow, wireframes and concept finalised, we are able to
now start working on the application’s aesthetics covering all the edge cases and user scenarios.
And showcase the screens as per the dates in the design plan.
And showcase the screens as per the dates in the design plan.
Now the designers stay in the creative den for whole 3 weeks!
The 
Dev Sprint Starts!
With the designs completed and signed off by the client, the screens and the
assets are picked up and sent to the Dev house. The Dev team breaks up the features and builds
them
in instalments with every sprint of 10 days.
During this timeline, the designers continue to stay active as now they have
an important task on their plate!
Oh! and sometimes the designers could be adding creative elements for their
individual expression.
for Every dev sprint
We do a round of
UI Testing
As the designs are thoroughly assessed and signed off by the client, its
essential for us to ensure the product that goes through the development, mirrors the original
designs. For this, in each sprint the designers do a UI check before sending the build to the
client.
The bugs are assigned to dev on
JIRA
Comparing the build with the Design to check if there are differences!
A Realistic shot of how things go during the
Dev Sprints
Find plugins for graphical charts used in designs.
A day when you don’t feel creative!
Developer frowns as the designer got a new idea and needs to make a minor change to the designs!
Ui bugs are logged on JIRA to be resolved by the DEV TEAM.
Way too many cups of coffee!
-This was for
Design & Dev projects.
Design & Dev projects.
& For Dlesign Only
The designs match and
A Pixel Perfect build is delivered
For a Design only Project
A Clickable Prototype is delivered
We sign up for an engagement of 3-4 weeks, starting with week 0 for
brainstorming and creating a design plan. Next 3 weeks are for designs and requirement gathering
in
parallel. By the end of this engagement, around 40 screens are designed.
& that includes the FRD
with the all the approved feature sets!
with the all the approved feature sets!
-That’s all for the process!
Oh! and sometimes depending on a project size & requirements, the timeline might slightly vary.
*
FRD is a functional Requirement Document that is made to capture all the requirements discussed
during the project timeline.