Embed Size (px)
Transcript of Modelling Personalization
- 1. Im not you Modelling and conceptualizing personalization in information architecture Presented by / Bogo Vatovec Change Management / Knowledge Engineering / User Experience / Interaction Design / Process Engineering
- Integration of personalization in a design of an interactive system.
What will I be talking about? 3. Personalization related deliverables
- Personalization Strategy
- Introduction to personalization
- Writing personalization scenarios
- Selecting the right strategy for my project
- Goals and KPIs
- Continuous Improvement program
- Conceptual models
- User, content and functional profiles
- Aspect-oriented use cases
- Personalization rules
- Probabilistic models
- Technology Selection
- Architectural requirements
- Choosing the tool
- Testing and Acceptance
Im going to skipthe red ones. 4. Introduction to personalization 5. Personalization can mean lots of different things to different stakeholders 6. Some of these cases are trivial If you are happy enough that they apply to you, forget the rest of the presentation. For the others 7. First some categorization No pretention that this modell is complete 8. Introduction how personalization works
- Personalization works essentially using the following methods:
- Explicit settings: I want A, B and C.
- Similarity of profiles: If A is similar to B then do C.
- Sequence of actions: If 1) and 2) and 3), then do 4).
- Combination of: If A is similar to B and 1) and 2) then do 4)
9. Explicit personalization the user chooses options 10. Implicit personalization 11. Most popular collaborative filtering
- If user A is looking at product 1 and has a similar profile to user B and user B also bought product1 and bought product 2, recommend product 2 to user A.
Example: collaborative filtering 12. Conceptualizing personalization 13. Conceptualizing personalizationhas one basic rule Describe behaviour without and with personalization separately. 14. Separate behaviour without and with personalization Withoutpersonalization,the user experience looks like this.. With personalization,the user experience looks like that.. Personalization expands the existing essential functionality. It is never a function on its own.The interactive system must serve its main purpose also without personalization. 15. IAs use common usage scenarios to define the context of personalization 16.
- Align personalization with the business strategy and desired user experience
- Is it important to have user profiles?
- Which data about the users is important?
- What kind of a benefit does the interactive system provide for the user and the business through different personalization types?
- Clearly state the personalization strategy by:
- Describing the personalization type used
- Describing usage scenarios illustrating the experience
- State the benefits for the business and the user
- Make sure every stakeholder understands this
Make sure to consider the following 17. Visualizing the big picture 18. Conceptual models -a rich picture 19. Conceptual models A relationships diagram 20. Profiles, profiles, profiles 21. User profiles
- A0: Anonymous first time visitor
- A1: Anonymous returning visitor leaving traces
- R1: Registered user (essential profile)
- R2: Registered returning user (essential and extended profile)
- RP1: Registered returning user with behaviour (essential, extended and behavioural profile)
User profile ID Behavioral data Core profile Extended profile A0 A1 R1 R2 RP1 22. Content and function profile Content/function Attributes Tags Tag cloud 23. Example: Detailing the user profile 24. Clarify user profile management
- When is the user profile created?
- When is the user profile deleted?
- Can the user delete his profile?
- What happens to the content related to the user profile?
- How much can the user know about his profile?
- How can the user manage/modify his profile?
25. Its time for use cases and flowcharts 26. Use cases in Information ArchitectureIllustrative purpose only 27. Use case model allows us to better understand the interactive system generalize include A use case model consists of three main type of relationships: Illustrative purpose only 28. The aspects-oriented use case modelling gives extend relationship a dynamic dimension extend Illustrative purpose only 29. This dynamic dimension changes system behaviour 30. User profiles can be incorporated in the activity diagram For use case haters: Use the flow-diagramm connecting screens in the same way and create various flow for each profile-type 31. This is silly. Have no idea anymore what we are talking about 32. Bringing it all together in a readable form 33. Modelling using aspects-orientation provides several advantages
- Makes conceptualization and incremental detailing easier
- Enables iterative development
- Allows for functional reduction
- Allows for easier testing and verification
34. This was easy, wasnt it? Wait were are at the personalization rules? Wait were are the Bayesian models? Wait were are adaptive interfaces? 35. Personalization rules specify conditions when personalization applies
- Some examples
- If user is looking at content A and content B has similar tags, show content B as related content.
- If user A with profile A has click 1 then 2 then 3 and pauses for 2,5s here, show context sensitive help.
- In the conceptualizing process, we use a simple descriptive language like this.
- Notice example Number 2) it has a sequence of conditions. Will talk about this in a minute.
36. Lets move to technology a bitand then explore the rest 37. Personalization strategy defines the use cases for technology
- Capture user behaviour on the website and store it in the user profile.
- Dynamically generate content recommendations based on user behaviour in real time (in one session)
- Dynamically generate content recommendations based on the stored user profile.
- Provide for statistical analysis of user behaviour based on user profiles to expand marketing knowledge.
- Provide the user the possibilities to customize the layout of the home pages.
38. To come up with requirements, you need to further specify them 39. Technical architecture for personalization Users User interface Layer Personalization Profile LayerSpecific Values Vocabulary LayerAttributes Content UserProfile ContentProfile ContentAttributes UserAttributes Personalization Rules Personalization Rules Modified from the model by Argus Center for Information Architecture Analytics UserBehaviour ContentStatistics 40. How can this model help us?
- How much does one system require explicit user profile setting?
- How much implicit?
- How does it integrate with other systems to fill out the profiles?
- How does the system support vocabulary level personalization rules?
- How easy it is to automatically populate content values?
- What features does the personalization system include to manage controlled vocabularies?
41. Those of you who carefully listened notices that I missed an important compontent.. TIME 42. Until now we looked at the user and content profiles as one object with one stateSince the user profile has only one state, we forget the sequence of actions users decis