https://docs.microsoft.com/archive/blogs/angryidmguy/feed.xml Adventures in Identity and Security Wed, 17 Apr 2019 03:15:27 GMT en-US hourly 1 https://docs.microsoft.com/archive/blogs/angryidmguy/complexity-or-ease-of-use-decisions-decisions Thu, 16 Feb 2017 11:48:14 GMT https://blogs.msdn.microsoft.com/angryidmguy/?p=165 really needs.  In the case above, I actually rewrote everything and gave them a much simpler product in the long run, because of the lack of knowledgeable staff in the product, especially complex implementations of it. So, how do we resolve this? Again, look at what the client is asking for, and evaluate the staff that will be there when you are long gone. Can you train them to the level of complexity that the system will require? Is there enough time in the contract for you to not only develop the solution, but provide enough knowledge transfer for the staff to understand and support the system in the manner it's being developed? If the answer is no to either of these questions, look to adjust your solution or the schedule to allow you to accommodate. And remember...just because a complex solution would look cool, doesn't mean it's the best way to do it.]]> https://docs.microsoft.com/archive/blogs/angryidmguy/the-identitysecurity-challenge Mon, 16 Jan 2017 09:30:02 GMT https://blogs.msdn.microsoft.com/angryidmguy/?p=155 not about technology. That is very shocking for many people in our field, because our natural proclivity is to solve all problems with a technical solution. I have done many projects over the years, and I would estimate that around 80-85% of them have always come down to business process. Sometimes this is one of the more challenging pieces that you can encounter with a client as well, as they are expecting just a technical solution to solve all of their problems.  So, how do you adjust? The answer is not simple, and yet it is.  It all depends on the client.  How receptive have they been to any of the technical solutions that you have been proposing?  Has there been anyone that has tried to force a solution different than the one that has been proposed?  And I say that with the thought in mind of the protective mindset that client technology people can sometimes have.  And it's understandable from their point of view...here is a consultant coming in to change their environment. The ability to remove the idea of technology from the discussions is how I have been able to work through some of these challenges.  Start with the process, work backwards from there, and the solution creates itself.]]> https://docs.microsoft.com/archive/blogs/angryidmguy/adventures-in-identity Fri, 06 Jan 2017 13:21:30 GMT https://blogs.msdn.microsoft.com/angryidmguy/?p=135