Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Search the Community

Showing results for tags 'reflection'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Atlassian

Categories

  • Personal
  • Professional
    • Management
    • Requirements
    • Design
    • Development
    • Testing
    • Operations
  • Interesting
    • Atlassian
    • Invision Community
    • E-Commerce

Categories

  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Operations
  • Atlassian
  • Invision Community
  • E-Commerce
  • Affixes & Prefixes

Categories

  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Operations
  • Atlassian
  • Security
  • E-Commerce
  • Others

Categories

  • Thoughts
  • Debate
  • Health
  • Hobbies

Categories

  • Personligt
    • Åsikter
    • Humor
    • Spel
    • Träning
  • Allmänt
    • Internet
    • Program & tjänster
  • Intressant
    • Prylar
  • Professionellt
    • Management
    • Krav
    • Designs
    • Webbutveckling
    • Test
    • Atlassian
    • säkerhet
    • Förvaltning
    • Ehandel
    • Wordpress
  • Personligt_

Categories

  • Prologue
    • About This Book
  • The Tools
    • Jira Software
    • Confluence
    • Jira Service Management
  • The Inception Phase
    • Portfolio Management
    • Project Management
  • The Design Phase
    • Design as part of the Inception phase
    • Design as part of the Requirement phase
    • Working with design libraries
  • The Requirement Phase
    • Definition of Requirements
    • The four levels of Requirements
  • The Development Phase
    • Atomic design
    • Estimations
  • The Test Phase
    • The Definition of Test
    • Types of Test
  • The Operations Phase
    • Release Management
  • The Post Go-Live Phase
    • Incidents
    • Changes
  • Notes
    • My Muses
    • Research

Categories

  • Theme Building
  • Javascript Framework
  • CSS Framework
  • IPS: Pages
    • Database Templates
    • Block Plugin Templates
    • Page Templates
  • Custom Applications
  • Tips & Tricks

Categories

  • Professional
    • Consulting
  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Operations
    • Hosting
    • Security
  • Interesting
  • Atlassian
  • Invision Community
  • E-Commerce
    • CRO
    • SEO

Categories

  • Shared Hosting
  • Virtual Private Server
  • Cloud Hosting
  • Dedicated Hosting
  • Co-Location
  • Hosting Services

Categories

  • Professional
  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Operations
    • Security
  • Interesting
  • Atlassian
  • Invision Community
  • E-Commerce

Categories

  • Professional
  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Operations
  • Miscellaneous

Categories

  • Defects
  • Ideas
  • Development
  • ☑ Archive

Categories

  • Professional
  • Management
    • Agile
  • Requirements
  • Design
  • Development
    • Frontend
    • Backend
  • Testing
  • Operations
    • Security
    • Hosting
  • Interesting
  • Atlassian
  • E-Commerce
    • CRO
    • SEO
  • Invision Community

Categories

  • Professional
    • Management
    • Requirements
    • Design
    • Development
    • Testing
    • Operations
  • Interesting
    • Atlassian
    • Invision Community
    • E-Commerce
  • Miscellaneous
    • Fun
    • Games
    • Inspiration
    • Music

Categories

  • Jira Software Cloud Basics
    • Projects in Jira Software Cloud
    • Navigation in Jira Software Cloud
    • Boards in Jira Software Cloud
    • Filters in Jira Software Cloud
    • Dashboards in Jira Software Cloud
  • Jira Software Cloud User Guides
    • Working with Boards in Jira Cloud
    • Working with Filters in Jira Cloud
    • Working with Dashboards in Jira Cloud
  • Jira Software Cloud Project Admin Guides
    • Working with Project Settings in Jira Software Cloud
    • Working with People Settings in Jira Software Cloud
    • Working with Automation in Jira Software Cloud
  • Jira Software Cloud Admin Guides
    • Jira Software User Management
    • Jira Software Billing
    • Jira Software System
    • Jira Software Products
    • Jira Software Projects
    • Jira Software Issues
    • Jira Software Apps

Categories

  • Invision Community HTML Framework
  • Invision Community CSS Framework
    • Typography
    • Colors
    • Columns & Grid
    • Responsiveness
    • Forms
    • Datalists
    • Buttons
    • Messages
    • Miscellaneous
  • Invision Community JavaScript Framework
    • Invision Community UI Widgets
    • Invision Community Utilities modules
  • Invision Community CMS Pages
    • Invision Community Pages Basics
    • Invision Community Pages Templates
    • Invision Community Pages Tips & Tricks
    • Invision Community Pages Basic relationship
  • Invision Community Tips & Tricks

Categories

  • Design Guidelines
  • How to work with The Flexible Atlassian Setup
    • Portfolio Management
    • Visual Design
    • Requirements
    • Development
    • Test & Acceptance
    • Deploy & Release
    • Post GoLive Support
  • The Jira Software Cloud Setup
    • Introduction to the Setup
    • Issue Types
    • Issue Type Schemas
    • Workflows
    • Workflow Schemas
    • Screens
    • Screens Schemas
    • Issue Type Screens Schemas
    • Custom Fields
    • Field Configurations
    • Field Configuration Schemas
    • Permission Schemas
    • Notification Schemas
  • The Confluence System Documentation Setup
    • Introduction to the Setup
    • Architecture Section
    • Documents Section
    • Instructions Section
    • Quality Section
    • Requirements Section
    • Tecnical Documentation Section
    • Organization Section
    • Visual design Section

Categories

  • Professional
  • Management
    • Methodology
    • Leadership
  • Design
  • Requirements
  • Development
    • Frontend
    • Backend
  • Testing
  • Operations
    • Hosting
    • Security
  • Interesting
  • Atlassian
  • Invision Community
  • E-Commerce
    • CRO
    • SEO
  • Miscellaneous

Categories

  • HTML References
    • HTML Tags
    • Frontend Frameworks
  • CSS References
    • CSS Properties
    • CSS Methodologies
  • JavaScript References
    • JavaScript Objects
    • JavaScript Libraries
    • JavaScript Methodologies

Categories

  • Product Reviews
  • Company Reviews
  • Hosting Reviews
  • Personal Blog Reviews

Categories

  • Confluence Cloud Basics
    • Confluence Cloud Interface
    • Conflunce Cloud Spaces
    • Confluence Cloud Personal Space
    • Conflunce Cloud Templates
  • Confluence Cloud User Guides
    • Conflunce Cloud Macros
    • Conflunce Cloud Space Blog
    • Conflunce Cloud Space settings
    • Conflunce Cloud Space Pages
  • Confluence Cloud Admin Guides
    • Conflunce Cloud General Configurations
    • Conflunce Cloud Security
    • Confluence Cloud Look and Feel
    • Confluence Cloud Adminsitration

Categories

  • Tools
    • Professional
    • Management
    • Design
    • Requirements
    • Development
    • Testing
    • Operations
    • Interresting
    • Atlassian
    • E-Commerce
  • Methodology
  • Social Interaction
  • Areas of Expertise
    • Management
    • Design
    • Requirements
    • Development
    • Testing
    • Operations
    • Atlassian
    • E-Commerce

Forums

  • General
    • Open Forum
    • Support
    • Applications
  • Professional
    • Management
    • Requirements
    • Design
    • Development
    • Test / QA
    • Operations
  • Interesting
    • Atlassian
    • Security
    • E-commerce
    • Invision Community
  • Jobs
    • Looking for employee / consultant
    • Looking for Job / Assignment
  • Building The Site's Forums
  • Destiny 2's Discussions
  • The Journey's Discussions
  • Cinephilia's Topics
  • Diablo 4's Diablo 4 Topics
  • Shadownessence's Topics
  • sensory hyperreactivity's Topics
  • Wolcen's Wolcen Topics
  • Quality Assurance Heroes's QA Topics
  • Visual Studio Code's Forum
  • Adobe Illustrator's Adobe Illustrator Forum
  • Sketch Guru's's Sketch Topics
  • Requirements & test management in Jira's Topics
  • Microsoft Teams's Microsoft Teams Discussions
  • Figma's Figma Topics
  • Microsoft Planner's Microsoft Planner Topics
  • Psychology's Psychology Topics
  • Microsoft Word's Microsoft Word Topics
  • Microsoft Powerpoint's Microsoft Powerpoint Topics
  • WordPress Devs's Wordpress Topics
  • Ornamental Design's Ornamental Design Topics
  • Adobe Photoshop's Photoshop Discussions
  • Agile 2's Agile 2 Topics
  • Agile 2's Agile 2 Principles
  • Microsoft Outlook's Outlook Topics
  • My Book's Discussions
  • Outriders's Outriders Discussions

Categories

  • Jimi's Files
    • Curriculum vitae
    • Presentations
    • Certificates
  • Management
  • Requirements
  • Design
    • Fonts
  • Code
  • Test
  • Operations
  • Atlassian
    • Certificates of Excellence
  • Security
  • Ecommerce
  • Invision Power Services
    • JWSE Support Tickets
    • JWSE Task Management
  • Shadownessence's Files
  • WordPress Devs's Wordpress Files

Calendars

  • Project: JWSE Workboard
  • Project: JWSE Workboard
  • Community Calendar
  • Professional Events
  • Management Events
  • Requirement Events
  • Design Events
  • Development Events
  • Test Events
  • Atlassian Events
  • Operations Events
  • E-commerce Events
  • Invision Community Calendar
  • Destiny 2's Events
  • The Journey's Events
  • Cinephilia's premieres
  • Diablo 4's Diablo 4 Events
  • Agile 2's Agile 2 Events

Blogs

  • How to start your own blog
  • Sketch Blog
  • Building The Site's Blog
  • Destiny 2's Destiny 2 ramblings
  • The Journey's Stories
  • Diablo 4's Diablo 4 blog
  • Sketch Guru's's Sketch News
  • Requirements & test management in Jira's News
  • Agile 2's Agile 2 Blog

Categories

  • Movies
    • Action Movies
    • Adventure Movies
    • Animated Movies
    • Comedy Movies
    • Crime Movies
    • Drama Movies
    • Fantasy Movies
    • Horror Movies
    • Romance Movies
    • Sci-Fi Movies
    • Thriller Movies
    • Western Movies
  • TV Shows
    • Action TV Shows
    • Adventure TV Shows
    • Animated TV Shows
    • Comedy TV Shows
    • Crime TV Shows
    • Drama TV Shows
    • Fantasy TV Shows
    • Horror TV Shows
    • Romance TV Shows
    • Sci-Fi TV Shows
    • Thriller TV Shows
    • Western TV Shows

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 13 results

  1. Requirements are very important. In fact I would say that 95% of all failed IT projects can be traced to a poor requirement process. This is baffling because requirements are really not that complicated and yet I see people fail in organization after organization. After I started to look into the different flavors of Requirements I start to understand why things are so very hard to understand for many. There are such confusion about what type of work you should actually do, who you actually work for and what you actually should deliver. So let us define what a requirement is first: "A Requirement is a legal agreement between the requester and the performer." That statement alone will surely get a few people raising their eyebrow for the simple reason that it does not fit in their job description. Again this baffles me that we have so many different work description for a single discipline. My only explanation is that people are confused on what different levels you work with requirements. If we simply break down the three most common way of working I have seen: Facilitate, Investigate and Document. Then add it to the three common areas of work: Business, IT and translation between the two, then we can make a nice matrix. From there we can see what actual roles people have. For me I think that anyone working with facilitating meetings as their primary function is a manager. Anyone who just document the need is a secretary. Those two types of "requirement analysts" I see frequently and in my opinion we should make sure that we call them for what they are so people do not think that this is requirement work. In the investigative category it is common to work in all 3 areas depending on who you work for. Business analysts help business to define their need and IT analysts help IT define their need. This is however not requirements as their final product, but need. That comes BEFORE requirements. In this matrix we can see that the only role that actually work with requirements as the final product are the Requirement Analysts. This makes sense since the definition of requirements as a final product is: "The outcome of a Requirement is a translation between need and realization of that need." This is where many fail. I see many, many requirements that are nothing more than a granular break down of a need, but lacking the translation. Many are often either to undefined and border on a business need, or other times I see technical specifications instead of the need. My theory is that people do not understand what requirements are and who they are for. We can see this in the delivery of requirements as well. I do not know how many times I have seen people claiming to work with requirements simply dump a bunch of documents on the development team and move on to next project, or next iteration of the project. This way of working when you build walls and throw packages over it is NOT a proper way to work with requirements. As we can see in the matrix above a requirement analyst sit between business and IT. There she function as a bridge between the two, translating need in both direction to ensure everyone understand and agree on what should be realized. This can only be done with active communication, person to person, and you never deliver a requirement, you make a handover. I think that this is the key for making requirement processes work: handover and asking development and test to take over the responsibility of the requirement. To ask the most important question there is: "do you understand what business want and can you realize that need with the information you have been provided?" If the answer is no to that question, then you are not done with the requirement. If you just understand your place in the requirement process and you understand what a requirement is, then the requirement process will be easy for you. If your organization understand that as well, then life will be great for everyone. So do you still think requirements are difficult?
  2. In the midst of all the terrible events in the world with Corona virus and things like that I find myself really enjoying life as it is. I work in a project that is chaotic and time pressed, yet it is actually one of the more enjoyable projects I have had in a long time. I am having a blast. It is always fun when I take on a temporary assignment doing design again. These projects are usually smaller in both scale of delivery and the number of people involved. They are also usually more chaotic and most of the time subject to a bit optimistic time estimation. This might seem like they would be negative experiences, but they almost always come with a very positive attitude. In this project for example we often get compliments and positive feedback from the client. No matter how chaotic things might be everyone in the team get things working and help each other out. Never will you hear complaints or see anyone pointing fingers. If you never try to step down for a while and renew your energies, then you are surely missing out. Even now that I have quit my job and with the Corona virus running rampant I am still the most relaxed I have been in quite a while. I get to dig into Sketch deeper and building things with Angular Materials that people will use every day. What can be better than that?
  3. In the last month I have been working on this site to try to figure out how to build things properly.I have made some adjustments to colors, built a brand new header and finally got the graphics I need to get content flowing. It has been some ups and some downs, but overall I feel pretty good about the way the site is coming together. Maybe the biggest change that happened in January was a shift in mindset. Going from always strive for perfection to good enough with the possibility to improve, really meant a lot. The other thing that really made a huge difference is getting PhpStorm and starting to code for real. Sitting in a proper IDE and do code, there is no feeling like it and I really, really missed it. Getting a ton of graphics also did matter a lot. That is because now I have the graphics needed to build the page heroes so I can start to feel a bit productive again. It also give me a ton of new graphics to use for articles and blog posts and it inspire me quite a bit to be honest. Great artwork always have that effect and not that I have a whole lot of new vectors to play with I have so many options while still being able to keep the site consistent. January was also a shitty month when it comes to stress and that affected things quite a bit. A work related issue really frustrated me and cost a ton of energy. My son is also having issues with school and live in general which takes a lot of time and make me worry of course. Fortunately he is an amazing person and I am constantly amazed over how mature he is despite his situation. So I have mixed worry and stress with a sense of pride and amazement, which has not really done wonders for my state of mind in January. Still, it's being handled and I feel a whole less stressed these last few days. Using Jira for Backlog management In theory this works great, but in reality I have been to lazy to use it properly. In February I will take it a bit more serious and I aim to do one story from the Epic "JWSE Website" every weekend as a minimum. I am also going to start my blog series on how to use Jira for site management, so the workflows will be updated a bit with a proper workflow. My highest priority right now is to add a home navigation for areas that are "generic". This includes things like Policies like Privacy Policy and an About This Site page where you will learn more about this site. These are being created slowly. Adding content headers to all sections This is what I am currently working on. The problem I am trying to solve is to how I will get this consistent across the site. For pages it's easy. Just drop in a component in the widget area and you are done. For databases I have to split out the templates for each database. That way I can add a component in the front page only and keep the data entries without a component. I may also try to add a section for each category, but that require some additional work with some if queries so it's not really a priority. The biggest issue I have right now is the application specific sections. While each application have their index file it is already added to the content wrapper. This makes it impossible to break out to be a full width container. The option will be to add a bunch of targets in the templates or if I can add it to the blocks themselves. I am trying to figure this out, but it should be possible even if it may not be a super clean solution. The other issue is that I have the CSS added in a separate file and there is no good way to add that to the applications. I might just lift this into the overall CSS since it's not a whole lot of CSS and I will add it to pretty much all pages anyway. Another option is to include it inside the block itself, but I do not like the idea of inline CSS. We'll see how I figure it out in the end. Recreating the projects database The projects database is going to be a focus area in February. in January I started the remake by adding content that follow the same format as the CV's we have at Zington. So besides adding the content I will also add new banners for each project using the new standard where the site icon is colored based on the area it is connected to. I also started to add some people from the People database so as I recreate the projects I will also list the people I currently have added. The ones not yet added I will see if I can add to the database. Not everyone will be added of course, but a few selected ones would be nice. I also want to connect the databases a bit better. Right now I just pull in the author image using the standard Invision Community template for profile. This I want to change a bit so I can link to the page in Awesome People rather than the user profile for the site. So January was a bit of trial and error, but things are slowly improving. I just need to focus on building content and not to try to get people in here to interact. It is for me I build this after all and if someone else like it, then great. I will not stress about it however. Just have fun and always strive for progress and not perfection.
  4. Another week have passed and as usual I have kept busy with the site. This week I did not feel great as I got a little bug that the family left behind, but it's one of those that just make you feel miserable. Still I had some nice progress on things here and things are looking pretty good. I started the week by looking over my content sources and decided to upgrade my Feedly account again. It cost a bit, but I think it will be worth it as I now can have a better inflow of content. Since a lot of interesting things comes in, but not really something I want to write about myself, I tested out a new format called Happenings of the Week. This allow me to create a curated list of interesting content that hopefully will be interesting to the people visiting the site. This also made me look into MailChimp again to create a newsletter for this type of content. I have not upgraded yet as I do not have that many users yet and the basic templates is ok for now. I will send this out weekly, probably on Sundays so I have time to manage it without feeling stressed during the week. I will also have a weekly blogpost of course if you prefer that. Over at Shutterstock I am still trying to fill up the 750 images so I can purchase that. It's surprisingly difficult when you do not really know what you need. I try to spread things out across the different content areas, but still 750 images is a lot! As far as the site goes I keep adding content and things feel great. I have some areas that need some extra love, but I am in no hurry. There are some design flaws, but as I am looking into a design update during 2020 anyway I will fix that then. The big changes I will make is to change the header a bit and then edit the templates a bit to add a header section in the content areas. This will allow me to organize things better and I can differentiate content a bit better. Overall I have posted 5 blog posts this week in the Blog Articles section and that is I little more than I planned for. There is just so much to write about however, so I do not feel there is any shortage on that front yet. I even joined some subreddits where I get a ton of ideas and inspiration to complement the content I get from Feedly. On the Peoples section I have a backlog of people that want to be presented. It's kind of nice and I have a little special thing I would like to do for the People section later. It require some planning, but it should be fun I think. For now I have more than enough to add people on a weekly basis, which is nice. I do plan to add a few new things to that section, like a section for my comments and some links to more social media like Behance, Instagram and Dribble. So this week has been great so far and next week is hopefully even better. How was your week?
  5. Requirements are very important. In fact I would say that 95% of all failed IT projects can be traced to a poor requirement process. This is baffling because requirements are really not that complicated and yet I see people fail in organization after organization. After I started to look into the different flavors of Requirements I start to understand why things are so very hard to understand for many. There are such confusion about what type of work you should actually do, who you actually work for and what you actually should deliver. So let us define what a requirement is first: "A Requirement is a legal agreement between the requester and the performer." That statement alone will surely get a few people raising their eyebrow for the simple reason that it does not fit in their job description. Again this baffles me that we have so many different work description for a single discipline. My only explanation is that people are confused on what different levels you work with requirements. If we simply break down the three most common way of working I have seen: Facilitate, Investigate and Document. Then add it to the three common areas of work: Business, IT and translation between the two, then we can make a nice matrix. From there we can see what actual roles people have. For me I think that anyone working with facilitating meetings as their primary function is a manager. Anyone who just document the need is a secretary. Those two types of "requirement analysts" I see frequently and in my opinion we should make sure that we call them for what they are so people do not think that this is requirement work. In the investigative category it is common to work in all 3 areas depending on who you work for. Business analysts help business to define their need and IT analysts help IT define their need. This is however not requirements as their final product, but need. That comes BEFORE requirements. In this matrix we can see that the only role that actually work with requirements as the final product are the Requirement Analysts. This makes sense since the definition of requirements as a final product is: "The outcome of a Requirement is a translation between need and realization of that need." This is where many fail. I see many, many requirements that are nothing more than a granular break down of a need, but lacking the translation. Many are often either to undefined and border on a business need, or other times I see technical specifications instead of the need. My theory is that people do not understand what requirements are and who they are for. We can see this in the delivery of requirements as well. I do not know how many times I have seen people claiming to work with requirements simply dump a bunch of documents on the development team and move on to next project, or next iteration of the project. This way of working when you build walls and throw packages over it is NOT a proper way to work with requirements. As we can see in the matrix above a requirement analyst sit between business and IT. There she function as a bridge between the two, translating need in both direction to ensure everyone understand and agree on what should be realized. This can only be done with active communication, person to person, and you never deliver a requirement, you make a handover. I think that this is the key for making requirement processes work: handover and asking development and test to take over the responsibility of the requirement. To ask the most important question there is: "do you understand what business want and can you realize that need with the information you have been provided?" If the answer is no to that question, then you are not done with the requirement. If you just understand your place in the requirement process and you understand what a requirement is, then the requirement process will be easy for you. If your organization understand that as well, then life will be great for everyone. So do you still think requirements are difficult? View full blog article
  6. Last Thursday I had my first meeting with the Claremont UX group that I am now a part of and it was one of those meetings where you just sit and go "wow" because your co-workers are just the greatest people you have ever met! While the UX part of Claremont is fairly new the people are sharp and experienced wizards for sure. The exchange of knowledge was through the roof and the level of discussion was at the highest level! It's been a while since I was not the sharpest UX mind in the room so sitting with these great minds was just amazing. I look forward to be a part of this group who truly is passionate about making the world a better place by making it as user friendly as possible. I see no limit to the amazing things that we can do together and my heart is just glowing with inspiration and passion right now. I can't wait to get to work on Monday! ... My new co-workers completely rocked my socks and it was epic!
  7. UX design, visual design, interaction design, creative technologist, GUI designer, usability consultant, information architect. The titles are endless these days and as someone who work with all of these pretty much every day I am starting to wonder if we are breaking things down to much these days, or if it is actually necessary to get things done? 10 years ago most of these titles were pretty uncommon, at least compared to the way they are used today. They still existed, they just were not as clearly defined and separated as they are today. Most just called themselves "designer" and that was pretty much ok. When I had my own design business there was no distinction between a visual designer or a UX designer for example because without the knowledge of one you can not do the job of another. Without knowing the information structure and the technical limitation of the platform I am designing for, I can not set the interaction design. Without the interaction design I can not set the UX and without the UX I can not set the visual design. It's not quite that linear as they all blend on multiple levels, but you get the idea. So for me these things are always connected and maybe that is why I never felt comfortable focusing on just one area. How can I best help a client if I do not understand the whole picture? How can I create a solution without understanding everything from psychology to visual principles to information architecture and interaction patterns in the different touch points in a customer journey? As the fields expand rapidly, just as they do for front end development, the information flow becomes almost unmanageable. Is this perhaps the reason why we see people that proclaim to be UX designers, visual designers or interaction designers? Or is it just that they still are "designers", but just focus on one area of expertise more than the other fields? Unfortunately I see a division, just like the division happening for the front end developers, where we have designers that put the creative power of the visual design as their only craft and others with the intellectual focus of interaction and psychology as a separate craft. I have been in projects where this division have worked fine and I have been in projects where this does absolutely does not work at all. It all depends on the people and the methodology where communication is always the key. As we dig deeper into the psychology of design and user behavior, for the web in general and e-commerce in particular, does this mean that it become to difficult to stay on top of the development in all these fields so a division of discipline is required? The tools we use suggest the opposite however and the borders between visual deign, interaction/UX design and even code becomes more and more blurred. So from a technical point of view we move towards where I was 10-15 years ago where you are doing just "design". As of now I am not really sure what is the best way moving forward. Is it better to have very focused individuals that form teams to get the full width of the design process? Or is it better to have less focused individuals that can handle the full range of disciplines on their own? What does this mean for methodologies and work processes, does it matter at all? What are your thoughts on this matter? What direction do you think we are headed and how do you feel about that?
  8. As I am leaving the current project, due to the fact that I am leaving for another company, other people are taking over my duties and I get less and less involvement in the work that I used to hold together as the spider in the web. This is very difficult as I am used to be the one in the center of all things and now I am on the outside. The new team lead do things differently and the process of change always leave a residue of confusion and every fiber in my body just want to step in and "fix" things. The thing is that there is nothing to "fix", it's just change and the fact that I no longer sit in the center of the project any more. The new team lead have things well under control and the project is doing just fine without me. The realization that you really are not that important is both liberating an a bit sad. On one hand I am glad because it means that I have succeeded in making myself obsolete and the team no longer have need of my guidance. They work just fine without me following the processes and workflows we have built together. On the other hand I feel a bit like a parent no longer being needed by their children and they move from home. Just in reverse as I am the one leaving. It's a bit sad to realize that you will no longer be the one they come for when they need help or the one they turn to for advice and comfort. “When you talk, you are only repeating what you already know. But if you listen, you may learn something new.” While this is a strange and sometime uncomfortable situation it is also a great opportunity to observe and learn from the new team lead and also to lift my gaze and look at things outside my part of the project. It's quite interesting and it's a very good learning experience, especially when you can pick up on body language. I see so many things now that I have not yet had time to observe before and it give me a wealth of new insights. So I am in a position right now that feels a bit weird, mostly because I am not just leaving the project, but the company as well. It's also sad as I have to much time to think about how much I will miss my team and my co-workers when I leave. Have you ever been in the same position and what did you learn from that?
  9. Building this new site feels amazing, yet very confined at times. Simple things that I have been used to are simply not part of the infrastructure. Other things are just different and things I wished I had a long time ago. Overall this is just the beginning of building a new beginning for my website. As with my old site I am still a bit all over the place when it comes to what I want the site to be about. I have already started to add my project portfolio and of course this blog, but beyond that I still play around with different things. Downloads are always nice and I have some thoughts on what I would like to do with that. The Gallery is just a dumping ground for images at the moment, pretty much like Facebook used to be. We'll see how much effort I want to put there later, but for now it will just be the way it is. The forum is a hub for conversation. I have added the "Ask Jimi" function I have been pondering on for a while. I also add sections for community discussions even if I don't know if that will ever pick up. Clubs are there of course as mini-communities. I have them mostly for the Atlassian Usergroup that I am leader for, but we'll see what else we can use it for. Calendar can be used for events, but I am not going to put that much effort into it right now. In the future it can be extended to different types of events to make it more useful. I do have the commerce part added to this site as well. It can be used for a great deal of things like donations or actually selling physical and digital things. As my book comes along, maybe I'll add it here and maybe it can be used to sell things like art or designs in the future? We'll see what can be done and I have some ideas that are connected to the downloads section. I tossed in a videos section because I love the simplicity and the fact that I can keep track of my own best videos in an easy way. Pages are the big part of this new site. It's a powerful application that you can use to build pretty much anything you want. The problem is that documentation is very poor and the community is not really active or helpful always. Despite this I find it very satisfying to try to figure out how to get the data I need to build the things I want. This blog is built on Pages, even though I have the blog functionality as an application as well. The reason is that I like the function to add a blog function to the clubs, but I find it lacking for my own blog. I also use it to build the database for project portfolio. Later I will build some new databases as well such as a code snippets database and a profiles database where I present and promote different people. For now I focus on the basics, but later on I will start looking at database relationship functionality to bring data from other databases into records. This is useful for example to bring in profiles into a project database or reviews into a blogpost. Over all I need to think about what I want to see here and why. Until I figure that out I will just continue having a good time posting blogposts, uploading videos and making status updates. It's such a nice feeling to have so many functions to play around with! ...but first I will go for a walk in the scorching summer heat and clear my head
  10. Building this new site feels amazing, yet very confined at times. Simple things that I have been used to are simply not part of the infrastructure. Other things are just different and things I wished I had a long time ago. Overall this is just the beginning of building a new beginning for my website. As with my old site I am still a bit all over the place when it comes to what I want the site to be about. I have already started to add my project portfolio and of course this blog, but beyond that I still play around with different things. Downloads are always nice and I have some thoughts on what I would like to do with that. The Gallery is just a dumping ground for images at the moment, pretty much like Facebook used to be. We'll see how much effort I want to put there later, but for now it will just be the way it is. The forum is a hub for conversation. I have added the "Ask Jimi" function I have been pondering on for a while. I also add sections for community discussions even if I don't know if that will ever pick up. Clubs are there of course as mini-communities. I have them mostly for the Atlassian Usergroup that I am leader for, but we'll see what else we can use it for. Calendar can be used for events, but I am not going to put that much effort into it right now. In the future it can be extended to different types of events to make it more useful. I do have the commerce part added to this site as well. It can be used for a great deal of things like donations or actually selling physical and digital things. As my book comes along, maybe I'll add it here and maybe it can be used to sell things like art or designs in the future? We'll see what can be done and I have some ideas that are connected to the downloads section. I tossed in a videos section because I love the simplicity and the fact that I can keep track of my own best videos in an easy way. Pages are the big part of this new site. It's a powerful application that you can use to build pretty much anything you want. The problem is that documentation is very poor and the community is not really active or helpful always. Despite this I find it very satisfying to try to figure out how to get the data I need to build the things I want. This blog is built on Pages, even though I have the blog functionality as an application as well. The reason is that I like the function to add a blog function to the clubs, but I find it lacking for my own blog. I also use it to build the database for project portfolio. Later I will build some new databases as well such as a code snippets database and a profiles database where I present and promote different people. For now I focus on the basics, but later on I will start looking at database relationship functionality to bring data from other databases into records. This is useful for example to bring in profiles into a project database or reviews into a blogpost. Over all I need to think about what I want to see here and why. Until I figure that out I will just continue having a good time posting blogposts, uploading videos and making status updates. It's such a nice feeling to have so many functions to play around with! ...but first I will go for a walk in the scorching summer heat and clear my head View full blog article
  11. As I am leaving the current project, due to the fact that I am leaving for another company, other people are taking over my duties and I get less and less involvement in the work that I used to hold together as the spider in the web. This is very difficult as I am used to be the one in the center of all things and now I am on the outside. The new team lead do things differently and the process of change always leave a residue of confusion and every fiber in my body just want to step in and "fix" things. The thing is that there is nothing to "fix", it's just change and the fact that I no longer sit in the center of the project any more. The new team lead have things well under control and the project is doing just fine without me. The realization that you really are not that important is both liberating an a bit sad. On one hand I am glad because it means that I have succeeded in making myself obsolete and the team no longer have need of my guidance. They work just fine without me following the processes and workflows we have built together. On the other hand I feel a bit like a parent no longer being needed by their children and they move from home. Just in reverse as I am the one leaving. It's a bit sad to realize that you will no longer be the one they come for when they need help or the one they turn to for advice and comfort. “When you talk, you are only repeating what you already know. But if you listen, you may learn something new.” While this is a strange and sometime uncomfortable situation it is also a great opportunity to observe and learn from the new team lead and also to lift my gaze and look at things outside my part of the project. It's quite interesting and it's a very good learning experience, especially when you can pick up on body language. I see so many things now that I have not yet had time to observe before and it give me a wealth of new insights. So I am in a position right now that feels a bit weird, mostly because I am not just leaving the project, but the company as well. It's also sad as I have to much time to think about how much I will miss my team and my co-workers when I leave. Have you ever been in the same position and what did you learn from that? View full blog article
  12. Last Thursday I had my first meeting with the Claremont UX group that I am now a part of and it was one of those meetings where you just sit and go "wow" because your co-workers are just the greatest people you have ever met! While the UX part of Claremont is fairly new the people are sharp and experienced wizards for sure. The exchange of knowledge was through the roof and the level of discussion was at the highest level! It's been a while since I was not the sharpest UX mind in the room so sitting with these great minds was just amazing. I look forward to be a part of this group who truly is passionate about making the world a better place by making it as user friendly as possible. I see no limit to the amazing things that we can do together and my heart is just glowing with inspiration and passion right now. I can't wait to get to work on Monday! ... My new co-workers completely rocked my socks and it was epic! View full blog article
  13. UX design, visual design, interaction design, creative technologist, GUI designer, usability consultant, information architect. The titles are endless these days and as someone who work with all of these pretty much every day I am starting to wonder if we are breaking things down to much these days, or if it is actually necessary to get things done? 10 years ago most of these titles were pretty uncommon, at least compared to the way they are used today. They still existed, they just were not as clearly defined and separated as they are today. Most just called themselves "designer" and that was pretty much ok. When I had my own design business there was no distinction between a visual designer or a UX designer for example because without the knowledge of one you can not do the job of another. Without knowing the information structure and the technical limitation of the platform I am designing for, I can not set the interaction design. Without the interaction design I can not set the UX and without the UX I can not set the visual design. It's not quite that linear as they all blend on multiple levels, but you get the idea. So for me these things are always connected and maybe that is why I never felt comfortable focusing on just one area. How can I best help a client if I do not understand the whole picture? How can I create a solution without understanding everything from psychology to visual principles to information architecture and interaction patterns in the different touch points in a customer journey? As the fields expand rapidly, just as they do for front end development, the information flow becomes almost unmanageable. Is this perhaps the reason why we see people that proclaim to be UX designers, visual designers or interaction designers? Or is it just that they still are "designers", but just focus on one area of expertise more than the other fields? Unfortunately I see a division, just like the division happening for the front end developers, where we have designers that put the creative power of the visual design as their only craft and others with the intellectual focus of interaction and psychology as a separate craft. I have been in projects where this division have worked fine and I have been in projects where this does absolutely does not work at all. It all depends on the people and the methodology where communication is always the key. As we dig deeper into the psychology of design and user behavior, for the web in general and e-commerce in particular, does this mean that it become to difficult to stay on top of the development in all these fields so a division of discipline is required? The tools we use suggest the opposite however and the borders between visual deign, interaction/UX design and even code becomes more and more blurred. So from a technical point of view we move towards where I was 10-15 years ago where you are doing just "design". As of now I am not really sure what is the best way moving forward. Is it better to have very focused individuals that form teams to get the full width of the design process? Or is it better to have less focused individuals that can handle the full range of disciplines on their own? What does this mean for methodologies and work processes, does it matter at all? What are your thoughts on this matter? What direction do you think we are headed and how do you feel about that? View full blog article
×
×
  • Create New...