Copy

Chandigarh Tech: Assets or Liabilities

We design an online registration form. A shopping cart. The weather notification filters. The rules that trigger emails in the CRM.

Are we really designing screens or forms?
For customers? For our managers? For our brand? For our RESUME too?

And, is our code an asset? Who owns it and for whom? For how long - for 18 hours or 90 hours.... before the manager says (and the team agrees) that we need to hide this field, change the validation, or disable the code?

As product team members, are we designing assets or liabilities?
Strong questions... 
OUTCOME gives you a chance to ask such questions, and to join us to find answers. At least directions if not the answers.

We need to sit, and so we need to book a seat.
Buy your tickets
to region's most promising UX Design conference, on 09 February.

You owe it to yourself.

Early bird spots are up for grabs. Get Your Tickets Today.

09 Feb 2019. Chandigarh.

- Vinish Garg, for the OUTCOME

Spread the OUTCOME Love

We are doing it on LinkedIn and Twitter. Join us to make it reach more people.
Copyright © 2019 OUTCOME team, at vhite, All rights reserved.


Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp