Information Architecture: Value Proposition of Our Approach

Information Architect um The Understanding Group, LLC
23. Feb 2016
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
Information Architecture: Value Proposition of Our Approach
1 von 49

Más contenido relacionado

Was ist angesagt?

Corporate Communications Today, Course Module 4: Innovation ManagementCorporate Communications Today, Course Module 4: Innovation Management
Corporate Communications Today, Course Module 4: Innovation Managementwi2
Corporate Communications Today, Course Module 4: Innovation ManagementCorporate Communications Today, Course Module 4: Innovation Management
Corporate Communications Today, Course Module 4: Innovation Managementwi2
Digital supporting pre post visit and classroom martin bazley upload versionDigital supporting pre post visit and classroom martin bazley upload version
Digital supporting pre post visit and classroom martin bazley upload versionMartin Bazley
Digital learning martin bazley gem conference swanseaDigital learning martin bazley gem conference swansea
Digital learning martin bazley gem conference swanseaMartin Bazley
Summer@UTS: Building your resilience for complexitySummer@UTS: Building your resilience for complexity
Summer@UTS: Building your resilience for complexitySimon Buckingham Shum
Four Ways to Find a JobFour Ways to Find a Job
Four Ways to Find a JobCareer Development Centre, La Trobe University

Was ist angesagt?(19)

Similar a Information Architecture: Value Proposition of Our Approach

Higher Education Website Best PracticesHigher Education Website Best Practices
Higher Education Website Best PracticesJim Black
Specialized Events: Meeting the Needs of your StudentsSpecialized Events: Meeting the Needs of your Students
Specialized Events: Meeting the Needs of your Studentsicice
Sloan C 2009   Meeting Students Where They Go   FinalSloan C 2009   Meeting Students Where They Go   Final
Sloan C 2009 Meeting Students Where They Go FinalLisa D'Adamo-Weinstein
Using e systems to support student engagementUsing e systems to support student engagement
Using e systems to support student engagementBecka Colley-Foster
Career Guide 2014-15 Final VersionCareer Guide 2014-15 Final Version
Career Guide 2014-15 Final VersionVic Snyder
About+usAbout+us
About+ustheextraaedge

Similar a Information Architecture: Value Proposition of Our Approach(20)

Último

Catalogue rapido 2023_compressed.pdfCatalogue rapido 2023_compressed.pdf
Catalogue rapido 2023_compressed.pdfJoe Nguyen
Root cause of Magnetic Humming due to TransformerRoot cause of Magnetic Humming due to Transformer
Root cause of Magnetic Humming due to TransformerRekaNext Capital
Amazon A Plus Content Visually Appealing.pptxAmazon A Plus Content Visually Appealing.pptx
Amazon A Plus Content Visually Appealing.pptxSherylEleazar
Enceladus vehicle - Nasa challenge Super heavy logistics transport.pdfEnceladus vehicle - Nasa challenge Super heavy logistics transport.pdf
Enceladus vehicle - Nasa challenge Super heavy logistics transport.pdfAndresIborra2
Chat.pptxChat.pptx
Chat.pptxChristianFazio2
Metro-Goldwyn-Mayer.pptxMetro-Goldwyn-Mayer.pptx
Metro-Goldwyn-Mayer.pptxssuser88cf801

Information Architecture: Value Proposition of Our Approach

Hinweis der Redaktion

  1. The theme of world ia day this year is “Information Everywhere, Architects Everywhere.” The email I got described the theme further – it said, “Because of the ubiquitous nature of information, information architecture is not just practiced by specialists. Instead, we see information being architected by people holding all sorts of titles, coming from all walks of life.” This got me thinking about what makes an IA. Everyone does Information ArchitectING – you don’t even need a computer to do that! Far fewer people do Information ArchitectER
  2. And I’d argue that there is a toolkit difference, a mentality difference, a difference in the way of approaching the world
  3. And when I say Information Architect, I don’t mean it like a job title. Your job title may be UX Designer or Event Planner or Administrator or Product Owner - but the way you approach your world might be as an Information Architect. I mean Information Architect in the way people mean Engineer. When people say “Engineer” everyone has a stereotype of what that is, they think they understand the value of an Engineer. Dilbert is a great example of that stereotype. Engineer is an identity, a way of approaching the world, an affinity your friends and neighbors won’t let you forget.
  4. Last year at about this time of year my husband and I were sitting in the ultrasound room at the hospital excited to see our baby for the first time. Then the technician said – there are 2 in here! You’re having twins! I was speechless, lost for words like all the air went out of the room. But my husband knew just how he felt – he said “Well that’s efficient!” And every time I tell that story, perfect strangers will say, “He must be an engineer!” And he is!!!! At least, that is what his degree is in. He doesn’t describe himself as an Engineer. It is not his job title. His day to day activities aren’t what you or I would consider Engineering. Yet anyone who met him would guess he is an engineer. There is something we associate with an approach that leads us to think of someone as an Engineer. What exactly that is would be difficult to describe. The best summary would be that an Engineer approaches the world in a certain way. That they have a certain mindset. And that mindset is highly valued in our society. Of course you need an engineer on the project! No question. We here in this room are in a new-ish field that isn’t well understood by the world. It would be a relief to have our own stereotype – for people to say – “He must be an IA!” What might that definition, that approach that defines us look like?
  5. We have to sell our skill set all the time. We are more than our deliverables. We have to sell our process. We have to defend our ability to do proper discovery – stakeholder interviews, content audits, user interviews, modeling. Many of you in this room work in companies where your tasks are rigidly defined and your time is closely watched. I’ve given a few talks on the value of conceptual modeling – of working out the problem space thoroughly before designing solutions – and after each talk people tell me how difficult it is to make the case for conceptual work in their workplaces. The truth is, the activities that lead to deeper understanding and better solutions are also more difficult to explain, and more difficult to sell, than other more brass tax activities like wireframes and specifications.
  6. Many of you in this room are students at the start of your careers. You have a lot of knowledge gained through your courses, and that can make you feel like you should know the right answers. You hear questions like - What do you mean defining the problem? Why can’t you just build it? How many solutions could there possibly be? Why don’t you just know the right answer? It’s just a simple website, or app, or console, or on and on and on.
  7. IA isn’t about having the right answers, it’s about having the right approach that gets you to the right answers. And I hope this talk helps you defend the right to have that approach.
  8. We are the ones who care about figuring out why we would build something before building it. We are the gatekeepers that hold off the solutions, the how, until we know the what and who and why. And explaining that can be really difficult.
  9. Many of you are probably all familiar with pace layers. It is a way of expressing rate of change. Everything changes, but at very different speeds. Here in Brand’s diagram we see nature at the center. Nature changes slowly. Culture changes a little faster. And Fashion on the outermost circle changes quite quickly.
  10. What would an IA’s pace layers look like? I think the Desire to make the complex clear is our center circle. Clarity wins. For me that means clarity of meaning. We are building digital places – places people go to and interact with. The only building material we have is information, and the meaning of that information changes that building material. You can build a wall out of bricks and suddenly the meaning shifts and one of those bricks is a pony! Well that’s no longer a very good wall! In this room there is a feeling of togetherness, comradery – that we all agree that making clear things, good things, matters. That’s clarity wins What I want to discuss in Approach - Toolkit / Mentality / Orientation The difference between us and the Engineer or the physical architect is that our approach doesn’t result in something physical. Where there is a bathroom in the garage and none in the house everyone knows something is wrong! And everyone can see why an architect would model before building – building a house costs a lot of money, takes physical resources and space! I would argue that our Approach is even more crucial because we are dealing with the meaning, defining the meaning of things. That meaning changes when it is related to other parts of the world. There is a physics to meaning and structure and it is very, very possible to do it wrong – to mess up. A door is always a door to an architect – a door is not always a door to us. We can spend an hour with a room full of stakeholder making sure we all mean the same thing when we say the word door – and that time would be very well spent! A project has spun off course many a time because no one had the IA approach of exposing the parts, making sure we know what we mean when we say what we say, determining a system, ensuring the integrity of meaning is still intact. But this skill we have, this Approach, is very difficult to talk about. So let’s try.
  11. Imagine someone shows you a webpage or wireframe – this is vague intentionally They ask - What do you thin?
  12. Well, there are plenty of things you could say about the Application – how it adheres to and differs from the norm.
  13. You could recognize a standard layout and know they used Wordpress or an Axure library
  14. There are plenty of things you could saw about best practices – way to put a picture of “people like me” front and center!
  15. But when it comes to Approach you can’t say anything. You don’t know the answers to the WHAT questions - What are the parts of your business? Purpose? Mission? Who are your users? This is what I mean by approach. Sandwiched between our ideals about clarity and the practicality of best practices – what is our lens on life that encourages us to seek out answers to all the questions and compels us to sort them to revile their patters?
  16. Let’s talk more about this Approach pace layer There are 3 main chunks to this Approach It’s not a linear thing, but a cyclical process of Exposing the Parts, asking the stakeholders- are these the right parts? All the parts? What else. Then determining the system those parts suggest or form. Working out that system often results in discovering more parts. And discussing that system with the stakeholders yields further and further insights. Deciding together is the binding element of all the activities that occur within the approach layer ALL OF THIS IS IN SERVICE TO Defining meaning which is in service to Clarity
  17. To dig into these parts of IA Approach I’d like to talk about it at a high level by focusing on a non-digital project. Fort building! We all have an experiences with forts. We’ve played in them or even built them. There are many types of forts from cardboard to community playgrounds. Today let’s focus on the age-old backyard fort.
  18. The project of building a backyard fort has a lot of similarities to any digital project. There are users to consider, stakeholders to consult, tools to utilize, time constraints to adhere to, risks to mitigate, and budget constraints
  19. Ok, so first let’s discuss Exposing the Parts
  20. How do you find the parts? Mostly by Asking the right questions. That can take the form of literally asking questions in an interview, or by investigating questions on a website, or by performing a content audit, etc In our example project, you are building a fort. Here is some parts exposed by interviewing your child and your spouse. They, of course, wouldn’t literally tell you these parts. They would talk on and on about how they envision the fort looking, and what they want to be able to do with it. There would be a lot of HOW. Like “I want a slide that looks like a dragon I can slide down, but it never gets hot like the one at steve’s house.” Then it is your job, with your IA approach, to boil that down to Slide
  21. Once the parts are exposed, you can all talk about the same things with the same words Opportunity to ask more questions The biggest one being, is there something missing? But also, opportunities to get the right nuance – Affordable not cheap, Survey not look Clarifying further – tell me what swing means to you Ask ask and ask some more. We often start conversations with, I’m going to be dumb now in service to being clear – its really important that we nail down what we mean when we say what we say. Furthering the meaning
  22. Look -> Survey Cheap ->Affordable
  23. Here is an example from a digital project we did for a university. We interviewed lots and lots of stakeholders throughout campus, and then extracted their goals, aligning them when we heard more than one group state the same goal.
  24. In a digital project there is often more than interviews to pull parts from, there are also websites to scrape and other inputs like existing user research to consider. Here is another digital project where we started collecting all the words we found the organization used – and some natural groupings started to occur. This is the natural progression of exposing the parts where you start to determine the system
  25. Determining the System Once you have the parts, you can group and arrange them
  26. Here we see the parts from our fort interviews placed into one sort of system. It’s showing the relative importance of the parts and the major groupings they fall into. The dragon slide you heard your child describe was overshadowed by the numberous times they mentioned climbing. You spouse didn’t have any overlapping parts with your child, so you can split the goals into 2 big, clear chunks – Play and Safety
  27. Once the system is determined you can discuss the relationship between those parts and the new meaning it creates. A stakeholder may see something like this and say – wow, I don’t like the priority we are giving to budget constraints. Or, oh, now I see how my team feels the way things have been running make a lot more sense
  28. The list of goals in excel we saw earlier was later turned into this set of prioritized circles just like in our fort example. These are all direct stakeholder quotes in relation to each other. This gave us and the client’s digital team a guidepost to check decisions against throughout the project.
  29. You might also make a quick sketch of how these action goals relate to each other in sequence. Height is necessary to get to survey and hand and slide – so it’s natural to have climb lead to those parts. This particular action of determining the system would take you seconds, and would get your brain thinking in new and advantageous ways.
  30. Here is a system of parts from a past project. Clearly there are hundreds of parts that fall into 3 main categories. There are further categories exposed through color coding. And each part takes on addition meaning through its connection with other parts, forming a huge system that represents the client’s world. This might look like a tremendous mess, but its actually representing tremendous clarity. In one case our project got ended with this as the main deliverable and it lived on the client’s wall for years. They wrote us to tell us how often they referenced it when making implementation decisions or explaining the ecosystem to a new employee or determining where a new part fit into their existing world. This is not an ER diagram, it’s not about implementation. It is conceptual, much like the fort diagram. There are systems at play. Almost like physics. You can do it wrong. You can break it’s meaning. EXPOSING IT is critical!
  31. Deciding together happens throughout the project. Every example I’ve shown you today was shown to our clients as the work progressed. This ensures alignment and also shares the ownership of the decisions so that after we, as consultants, leave the project the stakeholders own their solutions. They know why decisions were made and why the structure is the way it is – making it more likely that the clarity we have achieved with endure.
  32. Word of caution.
  33. Criteria for making, criteria for what good is, criteria that determines is something works Not an engineering problem
  34. When there are tensions a great way of discussing them is through intension models. In our fort example there is discord between hide and surveil. You can’t see a hidden child, but hidding is part of playing. So where is the balance?
  35. Here is an example from a digital project showing real results. The stakeholders unanimously answered the question, and then the 9 answers were discussed. The group ultimately landed on medium global focus. Directionality on these tension points is required for a project to move forward. You can’t be all things to all people.
  36. So at our core we have Clarity. And we layer on an Approach that respect the seeking of clarity. Once we’ve exposed the parts, determined the system, and decided together we layer on best practices, tools, and application – all the while respecting the pace layers that came before. This results in great products!
  37. Maybe our final product would look like this.
  38. And the client knows what they are getting because it all maps back to the parts that were exposed and the systems that were defined that we all decided on together
  39. Remember my ultrasound story? My husband was being a stereotypical engineer in his response “well that’s efficient!” When once I recovered, I was a stereotypical IA! I started thinking about the ramifications of having two. Being a very budget conscious, my head first went to childcare. We were discussing it before we left the hospital parking garage.
  40. So first we laid out the parts We both planned to continue working, we had a budget for what we planned to spend on daycare. I actually had it all mapped out for kid 1 in 2015 and kid 2 in 2017 and projecting costs all the way through when they graduated from college. I’m a planner. I’m an IA. Well, now I was having twins. So the parts of what I was considering about childcare weren’t changed. Cost, schedule etc But their meanings were certainly changed. Schedule now meant getting 2 babies ready in the morning. Travel now meant 2 car seats and 2 hats and 2 coats.
  41. Our priorities on these parts also didn’t change when we found out we were having twins. But due to Cost being one of our biggest circles, daycare was out of the question. Daycare costs double for double the babies. A nanny coming to your home cost only marginally more.
  42. This shift from daycare to nanny though changes the meanings of these parts! Travel no longer means my travel with the boys – now it means my nanny’s travel. Does she have a reliable car that can get to our house in a snowstorm? Schedule is not longer 8-5 and we can’t be late – it’s more of a give and take where we respect eachother’s time and have to flex to eachother’s schedule. A daycare worker having to go to the dentist wouldn’t affect my schedule- but my nanny’s dentist appointment changes my whole week! We went with a nanny, she is great
  43. I hope all of this helps you to be more confident in your IA approach. That you are doing amazing things in this world. Determining meaning in service to clarity. Making the world be good.
  44. If I may add one additional point - We need to encourage and develop the IA tendencies in those around us. To grow those who do architecting into architects. There is no need to be competitive about this type or work. We are not making paper mache angels – the market for IA work is limitless. I strongly believe that if we became good at explaining the core of IA, and good at recognizing that core in others - If we got good at encouraging and complimenting those who are also trying to make the complex clear – If we do that there is no limit the the number of IA projects in the world.
  45. Bit.ly.wiada2_stream
  46. P.S. Often when people don’t see the value of IA, it’s because they view the project as simple. They think you are suggesting you need an architect to build a snow fort! Everyone understands you need a professional to build a business fort – this is an example from a children’s museum. Business forts have more requirements and higher risk (people sue!) Snow Fort Materials: Snow Audience: Maker Approval needed: None Risks: None Clean-up: None Who makes it: Anyone Business Fort Materials: Wood, Nails, steal beams, steal cables, etc Tools: Crain, Drill, etc Audience: The public – all ages Approval needed from: Business, legal standards Risks: Huge Who makes it: Qualified professional company
  47. P.S.S.