hook42 zero-to-go-pt1-business-v2

20
Hook 42 [email protected] Hook 42 [email protected] ZERO TO GO IN 13 DAYS A Case Study of Enmetric.com Part 1: The business stuff Aimee Degnan [email protected] Case Study: Enmetric.com 1

Upload: hook42inc

Post on 21-Aug-2015

479 views

Category:

Documents


0 download

TRANSCRIPT

Hook 42

[email protected]

Hook 42

[email protected] 1

ZERO TO GO IN 13 DAYSA Case Study of Enmetric.comPart 1: The business stuff

Aimee Degnan

[email protected]

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 2

Who are we?

Aimee

Kristen

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 3

Get hooked:Hook 42

Strengths

Drupal

Web Content Management

Enterprise Content

Publication

Custom Application Integration

Strategic Technology Leadership

Systems Architecture

Services

Zero to go

Second Opinion

Rescue Mission

Add-ons

Moving House

Helping Hand

Clients

Start ups

Small business

Midsize business

Enterprise

Education

Flexible.

Work smart.

Fix complex problems.

Integrate anything.

Culture chameleon.

Scale for growth.

Deploy correctly.

Work efficiently.

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 4

Presentation Takeaw

ays

• Correctly defining the project prepares you for success.

• You CAN do things Good, Right, and Fast.

• Not just the destination, but how you get there.

• Process, techniques and tools used.

• Ask us Questions along the way.

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 5

Client: EnmetricSystems

Business Need

• Upcoming conference• Large press release• 3 page HTML site from 2010• No one “got” what they did

Constraints

• Don’t bother our resources• Use newly final branding• Leverage existing, but dated, copy

Environment

• 3 business folks (sign-off)• 1 dev / designer• 2 ops-type people

http://www.enmetric.com

Green Technology

Plug Load Management

Hardware + Software

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 6

Zero to Go:What does it mean??

OM

G –

Wha

t

do I

need

??

Exi

stin

g S

ite

Tech

nolo

gy

Sel

ectio

n

Con

tent

M

igra

tion

Sta

rting

Fre

sh

Bus

ines

s

Req

uire

men

ts

Des

ign

Impl

emen

t

GO

!O

ngoi

ng

mai

nten

ance

Brig

ht F

utur

e

GO

FU

RTH

ER

!

Every project has a different “zero”.

Most projects aren’t at a true “zero” point.

“Go” can mean a lot of things.

Results may vary.

Case Study: Enmetric.com

-N ZERO +N

EnmetricStartEOB

May 23

Functional. Professional. Platform to grow.By 7 June 2012.

Today

Hook 42

[email protected]

Hook 42

[email protected] 7

Defining Scope: Chaos to Clarity

Total Project Scope

Presale In / Out Scope Definition

+ Kick-off

Implicit

Problems to Solve

Explicitly Requested

Sometimes clients don’t say everything that they need.

Defining the “problem” or need in context to the business helps inform the solution.

Understanding the business, as an implementation partner, will help you help your clients.

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 8

Enmetric.com Starting Point

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 9

Trust Me:Requirements are your friend.

Requirements docs:

Wireframes

Comps

Infra defined

Business Environment

Content Assessment

Technical Assessment

Strategic Vision

Reality: there are a lot of moving parts to account for, even for a small site.

Closing the knowing-doing gap: from initial engagement to fleshing out the details.

Sometimes it “sounds” bigger to the client than initially requested.

Essential in the learning process for the business.

Case Study: Enmetric.com

Brochure,Website,Articles

HTML vs Wordpress vsDrupal

Increase sales,Speed time to

understanding,Get employees

Hook 42

[email protected]

Hook 42

[email protected] 10

Eye Doctor:Honing Design Direction

Step 1: Inspiration• Closer to• Further from• Industry trends

Step 2: Structure• Pages needed• Info Architecture• Wireframes & Content Plan

Step 3: Design• Leverage branding & styles• Provide comps• Expect to tune CSS

People need to see and interact with “stuff” to know what it is about.

Baby steps. Taken very quickly.

Help digest change over time.

Essential in the learning process for the business.

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 11

Moving Fast:Project Roadmap

Scope Define

• Tech platform• Design• Biz Review

Implement

• Theme• Write Copy• Infrastructure• Biz Review

Tune

• Apply copy• Debug• Infra test• Secure• Performance• Site Content

Testing• Biz Review

Go Live!

• Really? Tonight?

• Sweet goodness!

Business Hand-off

• Tune content• Stylistic

adjustments• Training and

handoff

Simplicity.

Parallel work.

Clear decision milestones.

Flexible framework choices.

Early dependency identification.

Efficient work should be used in any project.

Case Study: Enmetric.com

May 23 May 29 June 2 June 3 June 5 June 18

PR – June 5Conf – June 10

Hook 42

[email protected]

Hook 42

[email protected] 12

How already?:Tools & Techniques

Wireframes & Content Plan• Omni Graffle (Sketchy)• 2 review cycles

Comps• Omni Graffle (design)• Colors, fonts, padding• 3 review cycles

Copy & Assets• Word• One review cycle in Word• Ongoing review on site

What is the fastest tool that we HAVE and CAN use quickly?

Word, Yo.

Structure Diagrams (OnmiGraffle)

Lots of screen caps. (SnagIt!)

Pretty Pics. (Adobe CS6)

MAMP and LAMP

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 13

Biz Prep:Getting Dev. Started

• Provided core functionality to development team

• Defined Integration Needs

• Quickly defined the content and general site structure

• Created infrastructure needs with Ops teams:• GIT• PHP Versions / Extensions• Ngnix• Memcached• AWS• Amazon MySql DB services

Get destination defined for framework choice.

Prepare for any infrastructure needs not “implicit”.

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 14

Biz Prep:Commence theming!

• Design based on the Quick IA / Structure (initial) and Content Plan

• Making it Responsive

• Expectation Setting:• Design fine tuning is in the site• Framework can provide changes in the future

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 15

Biz Prep:Education

• Created how-to documents in Confluence

• Role based documentation• All, Biz, Dev, Ops

• Role based training

• Train the trainer (at the same time)

Teach a man to fish.

Hands on training.

Reference materials for self service help.

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 16

Then and Now: Design

Old Site New Site

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 17

Then and Now: Content

Then

• Developer needed to code pages.

• Systems admin will FTP changes to GoDaddy.

• Broken Google Analytics.

• When was it last updated?

Now

• Messaging is clearer for the business.

• Targets each audience.

• Business updates a page in minutes.

• Integrated YouTube

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 18

Then and Now: SEO

Old Site

• Google, results page 5 on core terms

• Most results were other sites referencing Enmetric

New Site

• In 4 days, Google page 4

• In 5 days, Google page 2

• Now, Google page 1, 5th result, 3 results on the page

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 19

Then and Now: Analytics

Then

• 6-7 visitors ave, 20 daily visitors, at best

• Broken GA home page

• A lot of drop off

Now

• 30 – 50 average daily visitors

• 46% new

• Ave Visit Duration grew to ~ 5 min.

• Pages / visit ~4

Case Study: Enmetric.com

Hook 42

[email protected]

Hook 42

[email protected] 20

Takeaways:Good, Bad, and Meh

Good • Parallel Work• Omni Graffle• Clear Sign-offs• Drupal 7• Design tuning expectations• Research the industry

Bad • Going fast is OK for some, not for others.• Go-live too accelerated.• More involvement from complete biz team.• We like more testing to remove irritating bugs.

Meh. • Adding functionality = adding debug time.• “Implicit Requirements” to dev team• Provided more “road mappy” diagram for the biz.• Design.• Copy in Word. Good / Bad.• Google Docs.Lessons are always

learned.

Case Study: Enmetric.com