Your SlideShare is downloading. ×
0
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Taming the Beast: UX for Large Drupal Projects
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Taming the Beast: UX for Large Drupal Projects

785

Published on

Session given at Design 4 Drupal Camp, 2013. Discusses the difference between UX for smaller projects and larger projects, and outlines some ways to make it work.

Session given at Design 4 Drupal Camp, 2013. Discusses the difference between UX for smaller projects and larger projects, and outlines some ways to make it work.

Published in: Design, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
785
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Talk about saving time:Stakeholder discussionsDiscuss before you developSave trouble with database clogging, feature reverting, etc.Exceptions:When you have complex content relationships or many fieldsWhen you have something that requires interacting with lots of content in real time to see how Drupal handles it. Examples: Major GridsExamples: Batch Uploads
  • Many of your stakeholders won’t understand Drupal.Teach about structured content, beyond “pages.”
  • In a larger site, there will likely be a multitude of content creators. Part of your job as a UX Designer is to figure out what content they need to create, and to identify the best way for them to enter that content.Make use of fieldsets, custom fields. Teach them about how things fit togetherThink of content in “chunks”
  • Set boundaries and expectations up frontPick Your Battles
  • Your least favorite stakeholder will often be a key player in the project’s success.
  • Find ways to speak your mind without being a jerk.
  • Things will not always be that bad. Try to stay upbeat. Encourage the team.
  • Transcript

    • 1. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comTAMING THE BEAST: STRATEGICUX FOR LARGE DRUPALPROJECTSDani Nordin, the zen kitchen
    • 2. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comDaniNordin• UX designer, writerand teacher• Specialize in UX andInteraction Design forDrupal teams• Founder, the zenkitchen• Author, Drupal forDesigners series• Mother of thisadorable little diva tomy right ->
    • 3. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comUX DESIGN IS DIFFERENT WHENBUILDING LARGER SITES
    • 4. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comSmaller Project UX• Fairly predictable• Can do in small teams or solo• Easy to see patterns in functionality/content• Blog• News Page• Events, etc.• Often dealing with 1-3 stakeholders• Sites are often promotional, with limited functionality
    • 5. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comLarger project UX• Generally unpredictable—or predictable in reallyannoying ways• Team dynamics are important, but messy• Patterns constantly shift• Decisionmakers, stakeholders and client contactsconstantly shift• Sites involve increasingly complex functionality andcontent
    • 6. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comMAKING IT WORK
    • 7. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comHAVE A VISION AND A PROCESS.
    • 8. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comDISCOVERY IS EVERYTHING.
    • 9. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comSKETCH. OFTEN.
    • 10. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comPROTOTYPE OUTSIDE OF DRUPAL.(WITHVERYFEWEXCEPTIONS).
    • 11. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comCONTENT STRATEGY: NO, REALLY,IT’S A THING.
    • 12. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comCONTENT CREATORS ARE USERS,TOO.
    • 13. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comAND THEN…
    • 14. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comTHERE WILL BE BAD DAYS.
    • 15. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comTHERE WILL ALWAYS BE A NEWSTAKEHOLDER.
    • 16. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comPICK YOUR BATTLES.
    • 17. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comKEY DELIVERABLES
    • 18. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comPROTOTYPES
    • 19. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comDESIGN AND ARCHITECTUREWORKSHOPS
    • 20. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comSPECIFICATION DOCUMENTS
    • 21. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comARCHITECTURE DOCUMENTS
    • 22. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comROUTINE SANITY CHECKS
    • 23. tzk-design.com • Twitter: @danigrrl • dani@tzk-design.comYOU AREN’T CURING CANCER,YOU’RE BUILDING A WEBSITE.

    ×