I experienced a Web 2.0 marketing phenomenon today, powered by AdWords. For those that don't know AdWords, simply think of it as the advertising machine where Google makes there money from search. If you want to know more, there's a ton to be found on the web that explains AdWords far better than I.
So, I'm online searching for some Balsamiq plugins, I ran across an AdWords link that told me, very directly, that Balsamiq couldn't do the job for me, and I should switch to a product called iRise.
I'm always interested in new tools, so I checked out the link offered by AdWords. Clearly, iRise is a very robust tool. Does about 700 things I probably don't need, but looks great and is certainly something that will, as they say "scale with me".
As I browse, I really cannot tell how they see themselves as competitive with Balsamiq, but I keep looking. The more I look, the more features I find - an extremely robust, detailed application, clearly targeted at the enterprise and seemingly well done for that purpose.
Even though it feels a bit like Microsoft Office and it's well documented feature bloat problem, I decide I will download it and check it out. First, though, I wanted to know what comes after the 30 day free trial. No need to start this relationship if I know I can't maintain it after a few dates. As Dr. Phil might say, we should know if this is going somewhere....
Then I find it. I nearly fall off my chair. $7,000 for a single seat license. $7,000. I found 10 cars around Palo Alto (CA) for less than $7,000 in two minutes. $7,000! Now, you might be thinking "$7000 for enterprise software is not so bad, I've paid three times that before for large enterprise installations."
To be clear, it's not really the price (after the sticker shock!) that gets me, it's that they seem to have no real idea of their target market. Balsamiq is $79. That's right, they have an AdWords campaign against a competitor that is so far outside there price matrix, it's not worth even doing the math. Think about that again. They are paying to market against some who cost significantly less than the sales tax resulting from their product (With apologies to you, New Hampshire).
This shotgun marketing isn't appealing to me - it's concerning. I know they wanted to match on possible competitors, but they could have picked any number of solutions that were at least in their price range or target. They established a full campaign about Balsamiq, and in the end, what I really ended up thinking was "Wow, these iRise guys are scared of Balsamiq? Or do they just not know their target audience?"
There is no way I am their target market. This tells me there is little chance that future versions will really target what I (as only a $7000 professional user...) want to get from the tool, compared to the enterprise customers who must be spending hundreds of thousands of dollars. When Oracle XE markets against mySQL (prior to being one big somewhat-happy family), it makes sense. It's a product targeted to similar markets, has similar features and a similar pricing model. It represents choice for my end of the purchasing spectrum. Not just a wide ranging blanket thrown over all word-matches for "database".
Bottom line - I can purchase nearly 87 copies of Balsamiq or one copy of iRise. I am sure iRise is great - the screen shots look nice, the features are detailed and complete - but did this AdWords campaign really get them what they were looking for?
Do people who are searching for and/or considering using Balsamiq really justify an 87 to 1 cost increase? I am sure for the set of enterprise users that need those features, this is a well justified expense - but not those users who would choose Balsamiq in the end. They simply serve different parts (pricing) with different goals (enterprise vs. collaboration) of the same target market.
I wonder if they got any value from this campaign at all, or someone just feels good about having a "robust Adwords strategy". Just because you can use AdWords, doesn't always mean you should.
Follow-up:
Even more AdWords fun? When I decided to write this entry, and went back to find the original AdWords posting, and I got this link presented to me, for the same search (!) - honestly, I couldn't make this up:
Disclosure Statements:
To be fair to iRise, I rounded up. The price is actually $6995, not $7000. Since that $5 is about 16% of the cost of Balsamiq, it's probably important to mention (sorry, couldn't resist).
Also they do state they offer some mid-level pricing for "smaller companies". So maybe you can get it for only $4,000. Stil does explain how these guys serve the same market.
You can see the comparison to Balsamiq for yourself if you like, too. Just in case it's taken down, I've placed a picture of the key part of the page below. Maybe that is worth $6900 to you. Not to me.
Saturday, May 1, 2010
Sunday, April 11, 2010
Here's a tip
Today, I got a tip from a waiter, rather than the other way around.
It wasn't monetary; It wasn't even a fun experience. But it sure was a tip.
The tip? In a service relationship, simply making my problem your problem is the beginning of the end. The key part of Problem Management is the Management, not the Problem.
It was Sunday, and, I wanted breakfast anywhere that didn't include me cooking. Now, for where we ended up, Sunday morning is probably always a busy place at this establishment - it's a touristy place, and it was raining out - so a large number of wet, hungry, people were looking for breakfast and staying at their table longer than normal - it was a recipe for a stressful day at the breakfast stop for the staff.
Getting seated and ordering went as one might expect - busy, but not horribly long. However, after ordering, everything went down hill. This is only important to mention because it was clear the waiter, in the end, was not the source of the problem - we were seated and ordered fairly quickly. However, as business people we face this problem ever day - the problem in front of us is rarely one solely of our creation, but we are often responsible for the solution.
After waiting for a considerable amount of time, we had not heard anything from the waiter, staff, or anyone even semi-official looking. Heck, Flo or Alice from Mel's would have been a welcome sight. More importantly, the coffee cups had sat empty long enough that my clear-as-day caffeine addition was starting to kick in. With a five-year-old in tow, time was not on our side, and we inquired on the status of our order.
The response to the question was not exactly out of Miss Manners:
"I've got this table of six and that table of five and you'll just have to wait"
As you can probably imagine, this was not exactly delivered with a Coke and Smile. In fact, his complete disbelief that we'd even ask him might have been the most troubling aspect - as if we were not actually there, to, you know, eat.
Contrast this to the situtation a few weeks ago at a different establishment. My waitress probably took more time in delivering the meal, but was constantly at the table checking in - Did we have enough water? Did we need more bread? She updated, apologized, and just made us felt like she understood the situation. In return, I felt involved, connected, and understanding of her situation. In both situations we had a hungry five year old along for the ride. In only one case, did the server seem to notice and even acknowledge the elements of the environment.
I will return to only one of these establishments. As the consumer in this service relationship, that is my role - to choose where to consume (In this case, quite literally!)
So what can we (Re)Learn from this? We easily forget our role in a relationship. Most business transactions are not symbiotic - one side is the consumer, and the other is the producer. As the producer, you've got a role to consistently provide your best. Let me be very clear - I said "consistently provide your best", not "always be perfect."
How we handle stressful events, failure, and mistakes is part of how we provide our best. Here are some of my steps to trying to provide my best, even when I'm the cause of the original problem.
Sharing your problem is a start - but not the finish! Update, Update, Update
Both waiters should be applauded for being honest - although one had to be prompted. Acknowledging the problem quickly and head on is a great start. But, don't stop there. Understand what parts of the problem can be addressed quickly, which cannot, and provide constant updates with a clear message on what can be expected from you, the provider, in the solution process. It is critical to demonstrate that you understand the issue from the point of view of the other party, and understand your role in both the problem and the solution.
Be transparent in the solution, and invite people into the process. Agree to a communication plan and strategy with your consumers so they know when to expect an update from you, and, more importantly, they already have an idea of what you will be telling them. Focus on direct, personal communication mediums - avoid email and instant messaging like the plague, and focus on phone, video conferencing, and even face to face meetings if possible. Let them know you honestly and sincerely understand you have an effect on their business.
Having the waiter, or any member of the team, come to the table and simply acknowledge the problem and set some expectations on the solution, face to face, would have disarmed the situation. I'm just not that scary. I even brushed my teeth.
Validate the problem, and confirm it. Provide a solution, even if it's a horrible hack
This next step is a big one, and sets you apart from a company that listens and one that understands. Sometimes, we clearly rush to a solution without really understanding the problem from the point of view of the consumer and involving them in the process. This morning, I simply would have loved a refill of the coffee. Keep the coffee coming, and you're half way home.
Let's take a hypothetical, but all too familiar, software story. You've got a massive bug in a new release that makes all monthly reports crash. You just can't run them. The consumer, is, understandably, pretty upset.
Realistically, do you know what the bug is? Probably not, or you wouldn't have gotten here. You've tested, tried, unit tested (you better have!), simulated, and did everything in your release process. So what makes you believe you have the fix right in front of you? You never saw this problem coming.
At this point, you can deploy every resource you have on the bug. You can chase it up for endless nights. You know what the customer cares about? Where are my monthly reports! They don't care about your unit testing, your process, your bugs, Tomcat memory issues, or problems with the JDK. Yes, they want transparency on the process, but only in the context of their specific issues - the reports!
You must really understand the problem in their terms. Can you run those reports for them? Can you pull the data from the database directly? Yes, it's a horrible hack, but it's just for today.
You don't have to live with this solution, just don't die by the problem.
Coffee aside, I needed to keep a five year old from tearing apart the table. Do you realize how I would have killed for a crayon? That's a solution that had nothing at all do to with the number of tables, customers, or how busy the chef was. Solutions exist - if you understand the problem in the eyes of the consumer.
Work at the right pace - make sure you get it right!
Once the problem has been established, breathe.
Do it again - breathe.
You're going to need to focus your energy on the solution, so it's time to let go of the problem. Put away the feeling of anxiety and focus solely on the solutions you've communicated to the consumer. This is why the sharing and validation are so important - not only are you bringing the consumer piece of mind, but you are giving it to yourself, too. You need to put the problem behind you. There will be time to reflect later.
Don't get caught up in all-nighters, panic, yelling, and the general behavior that sets in during crisis. Focus on the solution, and take the time to do it right. Crank out the horrible hacks, work arounds, and manual processes you've promised to your consumers. Do this as fast as you can, but only at the pace that makes sense for the solution. Rushing to a solution that is untested, unproven, or fails only causes more problems just reduces confidence. Communication with the consumer - establishing a clear risk profile and clarity on why you are working at the pace you are - will buy you the time to get it right.
Focus on the solution only, and nothing else. Wallowing in the problem helps nothing at this point. Anyone on who starts in with "I can't believe we got here" and "I told you so" - they are off the solution team. I don't care if they created the problem, or are the smartest person you know. They are simply not in the consumer/producer solution frame of mind. Replace "I can't believe we got here" with "How did we get here? Did we miss something?" When they are ready to contribute positively, looking forward, invite them back in. Not before. Don't let a toxic thought into the solution team.
Enough Theory - Any Reality?
These are all wonderful concepts. There are people who have gone through much bigger crisis and much bigger issues than you, me, or anyone we know. But the reality is that each day threats to our business, our investments, and our livelihood is as big as Apollo 11 - to each of us.
In a follow-up post, I'll be discussing public and private JIRA instances and other tools you can use to be transparent, prove to your customer base you trust them, and treat the world around you like adults. Transparency, honestly, and trust is the key to any successful personal relationship. I believe it's the same for businesses.
Until then, I'll be looking for a crayon and some coffee.
It wasn't monetary; It wasn't even a fun experience. But it sure was a tip.
The tip? In a service relationship, simply making my problem your problem is the beginning of the end. The key part of Problem Management is the Management, not the Problem.
It was Sunday, and, I wanted breakfast anywhere that didn't include me cooking. Now, for where we ended up, Sunday morning is probably always a busy place at this establishment - it's a touristy place, and it was raining out - so a large number of wet, hungry, people were looking for breakfast and staying at their table longer than normal - it was a recipe for a stressful day at the breakfast stop for the staff.
Getting seated and ordering went as one might expect - busy, but not horribly long. However, after ordering, everything went down hill. This is only important to mention because it was clear the waiter, in the end, was not the source of the problem - we were seated and ordered fairly quickly. However, as business people we face this problem ever day - the problem in front of us is rarely one solely of our creation, but we are often responsible for the solution.
After waiting for a considerable amount of time, we had not heard anything from the waiter, staff, or anyone even semi-official looking. Heck, Flo or Alice from Mel's would have been a welcome sight. More importantly, the coffee cups had sat empty long enough that my clear-as-day caffeine addition was starting to kick in. With a five-year-old in tow, time was not on our side, and we inquired on the status of our order.
The response to the question was not exactly out of Miss Manners:
"I've got this table of six and that table of five and you'll just have to wait"
As you can probably imagine, this was not exactly delivered with a Coke and Smile. In fact, his complete disbelief that we'd even ask him might have been the most troubling aspect - as if we were not actually there, to, you know, eat.
Contrast this to the situtation a few weeks ago at a different establishment. My waitress probably took more time in delivering the meal, but was constantly at the table checking in - Did we have enough water? Did we need more bread? She updated, apologized, and just made us felt like she understood the situation. In return, I felt involved, connected, and understanding of her situation. In both situations we had a hungry five year old along for the ride. In only one case, did the server seem to notice and even acknowledge the elements of the environment.
I will return to only one of these establishments. As the consumer in this service relationship, that is my role - to choose where to consume (In this case, quite literally!)
So what can we (Re)Learn from this? We easily forget our role in a relationship. Most business transactions are not symbiotic - one side is the consumer, and the other is the producer. As the producer, you've got a role to consistently provide your best. Let me be very clear - I said "consistently provide your best", not "always be perfect."
How we handle stressful events, failure, and mistakes is part of how we provide our best. Here are some of my steps to trying to provide my best, even when I'm the cause of the original problem.
Sharing your problem is a start - but not the finish! Update, Update, Update
Both waiters should be applauded for being honest - although one had to be prompted. Acknowledging the problem quickly and head on is a great start. But, don't stop there. Understand what parts of the problem can be addressed quickly, which cannot, and provide constant updates with a clear message on what can be expected from you, the provider, in the solution process. It is critical to demonstrate that you understand the issue from the point of view of the other party, and understand your role in both the problem and the solution.
Be transparent in the solution, and invite people into the process. Agree to a communication plan and strategy with your consumers so they know when to expect an update from you, and, more importantly, they already have an idea of what you will be telling them. Focus on direct, personal communication mediums - avoid email and instant messaging like the plague, and focus on phone, video conferencing, and even face to face meetings if possible. Let them know you honestly and sincerely understand you have an effect on their business.
Having the waiter, or any member of the team, come to the table and simply acknowledge the problem and set some expectations on the solution, face to face, would have disarmed the situation. I'm just not that scary. I even brushed my teeth.
Validate the problem, and confirm it. Provide a solution, even if it's a horrible hack
This next step is a big one, and sets you apart from a company that listens and one that understands. Sometimes, we clearly rush to a solution without really understanding the problem from the point of view of the consumer and involving them in the process. This morning, I simply would have loved a refill of the coffee. Keep the coffee coming, and you're half way home.
Let's take a hypothetical, but all too familiar, software story. You've got a massive bug in a new release that makes all monthly reports crash. You just can't run them. The consumer, is, understandably, pretty upset.
Realistically, do you know what the bug is? Probably not, or you wouldn't have gotten here. You've tested, tried, unit tested (you better have!), simulated, and did everything in your release process. So what makes you believe you have the fix right in front of you? You never saw this problem coming.
At this point, you can deploy every resource you have on the bug. You can chase it up for endless nights. You know what the customer cares about? Where are my monthly reports! They don't care about your unit testing, your process, your bugs, Tomcat memory issues, or problems with the JDK. Yes, they want transparency on the process, but only in the context of their specific issues - the reports!
You must really understand the problem in their terms. Can you run those reports for them? Can you pull the data from the database directly? Yes, it's a horrible hack, but it's just for today.
You don't have to live with this solution, just don't die by the problem.
Coffee aside, I needed to keep a five year old from tearing apart the table. Do you realize how I would have killed for a crayon? That's a solution that had nothing at all do to with the number of tables, customers, or how busy the chef was. Solutions exist - if you understand the problem in the eyes of the consumer.
Work at the right pace - make sure you get it right!
Once the problem has been established, breathe.
Do it again - breathe.
You're going to need to focus your energy on the solution, so it's time to let go of the problem. Put away the feeling of anxiety and focus solely on the solutions you've communicated to the consumer. This is why the sharing and validation are so important - not only are you bringing the consumer piece of mind, but you are giving it to yourself, too. You need to put the problem behind you. There will be time to reflect later.
Don't get caught up in all-nighters, panic, yelling, and the general behavior that sets in during crisis. Focus on the solution, and take the time to do it right. Crank out the horrible hacks, work arounds, and manual processes you've promised to your consumers. Do this as fast as you can, but only at the pace that makes sense for the solution. Rushing to a solution that is untested, unproven, or fails only causes more problems just reduces confidence. Communication with the consumer - establishing a clear risk profile and clarity on why you are working at the pace you are - will buy you the time to get it right.
Focus on the solution only, and nothing else. Wallowing in the problem helps nothing at this point. Anyone on who starts in with "I can't believe we got here" and "I told you so" - they are off the solution team. I don't care if they created the problem, or are the smartest person you know. They are simply not in the consumer/producer solution frame of mind. Replace "I can't believe we got here" with "How did we get here? Did we miss something?" When they are ready to contribute positively, looking forward, invite them back in. Not before. Don't let a toxic thought into the solution team.
Enough Theory - Any Reality?
These are all wonderful concepts. There are people who have gone through much bigger crisis and much bigger issues than you, me, or anyone we know. But the reality is that each day threats to our business, our investments, and our livelihood is as big as Apollo 11 - to each of us.
In a follow-up post, I'll be discussing public and private JIRA instances and other tools you can use to be transparent, prove to your customer base you trust them, and treat the world around you like adults. Transparency, honestly, and trust is the key to any successful personal relationship. I believe it's the same for businesses.
Until then, I'll be looking for a crayon and some coffee.
Monday, December 10, 2007
The Screen Shots....
As promised, the screen shots of the first pass are attached. I don't believe they look very good, to be quite honest, but let's see if we can't make something of them, and then update the screens as we update the application, too.
The example is pretty silly, but it works - using the LocationManager and GPS tracking, the little "guy" icon has just passed two Peets coffee shops, depicted by the Peets logo on the map.
The key to this functionality is the extension of the Overlay class, allowing us to draw on top of the map. I have subclassed Overlay to IconOverlay and MultiIconOverlay. One consideration I wondered out-loud about (annoying the cat) - why not have multiple layers, like Photoshop, rather than a single Overlay that all items must stuff into? It didn't really create any problems for this simple prototype, however it did seem that being able to turn a layer/overlay on or off, rather than redrawing the entire set might be more efficient to the developer. For example, an overlay with all Starbucks locations, and an overlay with all Peets locations, and then simply invalidate the map with the Overlay(s) turned on you would prefer.
Anyway...the screen shots await:

For the record, if you are not from Silicon Valley and you are reading this looking for Peets, there are no Peets near this part of Bayshore. Seriously, wrong place to be looking for coffee. It's just a demo, people.
I'd like to note that the little "guy" icon came from FastIcon.com. I had not heard a thing about FastIcon until I was desperate for a cool little icon to represent the user as they made their way around the map. It was going to be a car or a person, and for the love of god, there was no way I was drawing it. And, the Starbucks' logo walking around finding the Peets logo just seemed wrong on so many levels.

I stumbled upon FastIcon and their license terms, and most importantly, I really like the comic/hip/modern look to the design, at least for this project. It's meant to be fun, and the icons on the FastIcon site certainly convey that. So, check it out if you are looking for some good icons.
The example is pretty silly, but it works - using the LocationManager and GPS tracking, the little "guy" icon has just passed two Peets coffee shops, depicted by the Peets logo on the map.
The key to this functionality is the extension of the Overlay class, allowing us to draw on top of the map. I have subclassed Overlay to IconOverlay and MultiIconOverlay. One consideration I wondered out-loud about (annoying the cat) - why not have multiple layers, like Photoshop, rather than a single Overlay that all items must stuff into? It didn't really create any problems for this simple prototype, however it did seem that being able to turn a layer/overlay on or off, rather than redrawing the entire set might be more efficient to the developer. For example, an overlay with all Starbucks locations, and an overlay with all Peets locations, and then simply invalidate the map with the Overlay(s) turned on you would prefer.
Anyway...the screen shots await:

For the record, if you are not from Silicon Valley and you are reading this looking for Peets, there are no Peets near this part of Bayshore. Seriously, wrong place to be looking for coffee. It's just a demo, people.
I'd like to note that the little "guy" icon came from FastIcon.com. I had not heard a thing about FastIcon until I was desperate for a cool little icon to represent the user as they made their way around the map. It was going to be a car or a person, and for the love of god, there was no way I was drawing it. And, the Starbucks' logo walking around finding the Peets logo just seemed wrong on so many levels.

I stumbled upon FastIcon and their license terms, and most importantly, I really like the comic/hip/modern look to the design, at least for this project. It's meant to be fun, and the icons on the FastIcon site certainly convey that. So, check it out if you are looking for some good icons.
First shots at an android application
I've decided to record my exploits with Android platform in blog form, hopefully giving back a bit to the community and getting feedback at the same time. I've actually already completed my first major Android application, and have a few classes I need to clean an publish. I still have plenty I want to accomplish with it as well, so it's best to get the blog started, and catch up the code, so to speak.
So, the goal - Build an Android application that does the following:
1. Display a map, and tracks you using GPS as you move around
2. Display a custom icon/graphic for "you"
3. Display a custom icon/graphic for what you are looking for (more on that in a second)
4. Store the possible sites (and site detail) in the on-board database
5. Click on/Select place on the map to view it's data from said database
6. Call the phone number of the place selected
Reasonable goal, eh?
I've accomplished 1, 2 and 3 using some fake data, so I decided to create a version that tracked all of the local coffee shops (Peets and Starbucks), and used their logos as the site markers. Since I already had done the tracking, IconOverlay classes, and custom images, this seemed like a very reasonable goal.
However, have you ever looked at Starbucks on-line store locator? It's really well done. It's a little slow, but it has built in mapping and route planning to find the closest shops, using the Live Search Maps from Microsoft. I can't complain. Therefore, it's a lot less motivating. I realize I'm not solving world peace here, but it would be nice to do something that has not been solved already, or at least not done so well. (Heck, Starbucks is even looking at the user-agent in the browser request and determining if they should return you a mobile-friendly page, similar to Google and the iPhone. Well played Seattle Siren, well played.)
So, I've decided to do this with just Peets Coffee data. Not that they haven't done a great job with their site, either. They are using Google Maps in their Store Finder, and it's well done overall.
In other words, maybe I should be doing a 7-11 locator or something other than the coffee shops, who seem to be using the collective free-WiFi as a breeding ground for map-mash-up-dudes and dudettes.
For the record, I've got no stake in either company, and frankly, my addiction to caffeine knows no bounds. Next post - the weekend work to bring the GPS tracking, Maps, and IconOverlay classes into being.
So, the goal - Build an Android application that does the following:
1. Display a map, and tracks you using GPS as you move around
2. Display a custom icon/graphic for "you"
3. Display a custom icon/graphic for what you are looking for (more on that in a second)
4. Store the possible sites (and site detail) in the on-board database
5. Click on/Select place on the map to view it's data from said database
6. Call the phone number of the place selected
Reasonable goal, eh?
I've accomplished 1, 2 and 3 using some fake data, so I decided to create a version that tracked all of the local coffee shops (Peets and Starbucks), and used their logos as the site markers. Since I already had done the tracking, IconOverlay classes, and custom images, this seemed like a very reasonable goal.
However, have you ever looked at Starbucks on-line store locator? It's really well done. It's a little slow, but it has built in mapping and route planning to find the closest shops, using the Live Search Maps from Microsoft. I can't complain. Therefore, it's a lot less motivating. I realize I'm not solving world peace here, but it would be nice to do something that has not been solved already, or at least not done so well. (Heck, Starbucks is even looking at the user-agent in the browser request and determining if they should return you a mobile-friendly page, similar to Google and the iPhone. Well played Seattle Siren, well played.)
So, I've decided to do this with just Peets Coffee data. Not that they haven't done a great job with their site, either. They are using Google Maps in their Store Finder, and it's well done overall.
In other words, maybe I should be doing a 7-11 locator or something other than the coffee shops, who seem to be using the collective free-WiFi as a breeding ground for map-mash-up-dudes and dudettes.
For the record, I've got no stake in either company, and frankly, my addiction to caffeine knows no bounds. Next post - the weekend work to bring the GPS tracking, Maps, and IconOverlay classes into being.
Sunday, October 23, 2005
Peter Forret's Web 2.0 Overview
For me, this is one of the best Web2.0 overview diagram. (with all due respect to Tim O'Rielly's meme diagram, which did get this all started). The single most important thing is the flow, and the realization of the differing categorizations of data sources, both trusted and non. The reason I liked this more than most of the Web2.0 diagrams is that it is the first to challenge my thinking and assumptions.
Specifically, look at the example sites of UserData - CraigsList and Wikipedia are both on the list. At first, I thought, "but wait, those are not user data" - and even went as far as to think there should be another source more clearly linked to "user" data. But I am wrong, and this is where Peter's diagram was inspiring.
Specifically, look at the example sites of UserData - CraigsList and Wikipedia are both on the list. At first, I thought, "but wait, those are not user data" - and even went as far as to think there should be another source more clearly linked to "user" data. But I am wrong, and this is where Peter's diagram was inspiring.
Web 2.0 Participation and Information Model
Dion Hinchcliffe's Web 2.0 Participation and Information Model
Originally uploaded by Dion Hinchcliffe.
Saturday, October 22, 2005
More on Flock...
I've been reading as much about Flock as I've been using, and the popular opinion seems quite mixed. Interestingly enough, the world seems to have wanted something very revolutionary, rather than evolutionary, which is most interesting. Also, the opinions seem to be mostly from Firefox users. In fact, I'm not sure I can find a review by someone that actually uses IE as their primary browser. Well, that's probably not fair...I am sure the folks at Business Week probably had to convince several layers of IT managment to allow them to use something other than IE.
One of the more practical reviews I read was by Dion Hinchcliffe. His review had a more reasonable "I know this is based on Firefox". His ideas are quite good, and frankly the comments on del.icio.us actually would make it interesting to me. Tagging, grouping, and more importantly, suggesting are the parts of del.icio.us that encourage me to share and involve - I'm getting something back. The currency exchange is clear. I add to the collective, and I get back. I'm very willing to be more organized and share with my fellow man if I can leverage the collective intelligence.
If nothing else, Flock has inspired me to dig a little deeper into some technologies I couldn't/didn't value previously. That certainly is a point for Flock. I need to spend more time with del.icio.us this weekend.
Thursday, October 20, 2005
Flock
I really want to like Flock. So far, it's nice and all, but I have not felt some huge "I've got to dump what I'm using" feeling, like I did when I started using Mozilla/Firefox. Just needs more time; I doubt that I had the clarity I seem to remember about Firefox, either. The inline blogging is certainly nice, and I'll keep pushing on the new features, and see what pops up.
Technorati Tags: Flock
First Entry
We all have to have one, right? So this is mine. Finally decided to move over to Blogger...Flock made me do it.
Subscribe to:
Posts (Atom)