I think the biggest problem anyone has with Wotc is communication. I know that when you’re owned by a larger company they set the rules, but even they must know that communication with customers is the key to success. There is and old saying “tells someone why you are making a change or have delays and they will still follow if not you have no followers”. It seem like Wotc needs to follow the model of penny stocks the more information you put out the more the stock goes up. It’s just simple give the customer value and communicate. I know some people on this forum go overboard with their comments and criticism but most just want to know what is going on.
Communication + Value + Deadlines = Success
Personally, I was very pleased with the communication in early Deecember, but it kind of degraded over the holidays to the point of being terrible again.
Personally, I was very pleased with the communication in early Deecember, but it kind of degraded over the holidays to the point of being terrible again.
Throw a few breadcrumbs to sate the starving and promise that a feast is just around the corner... and then start baking bread for more breadcrumbs.
(I'm trying to make this into an actual conversation)
I think there is some communication but it’s cryptic at best. Deadlines seem to come and go. A list of what bugs that have been fixed before an actual update would be nice. Things that are in progress etc. I will even take teasers with a little meat on the bone.
Can you point to a piece of communication in the last month or so that you think is cryptic? I'm interested in seeing a different point of view on this.
Of course, I think previews would be very nice and I hope it's something they could implement. I think it's the perfect use for the developer's blogs on this site. It's not something I'm particularly angry about though.
Can you point to a piece of communication in the last month or so that you think is cryptic? I'm interested in seeing a different point of view on this.
I’m not angry. I guess being a business man I’m trying to understand the business or communications model. The communication yesterday, I understand that they didn't like what they saw after the update but what bugs were the problem, how long is the delay not we hope to get it up this week. Can we drop the bug fixes that are causing the problem, so the update can happen? That's why I think it would help if they had an active bug page (even if the fix didn't make into the next update they could show insiders the progress) that list bugs that have been fixed before the next update. Anyone can be angry but that doesn’t solve the problem. Plus I think at this point it would be best for Wotc to be as open as possible to win back trust.
What is it that's lacking right now, LightAngel? What communication would you like that you haven't received?
(I'm trying to make this into an actual conversation)
An up-to-date known issues list, actually containing all the issues that are known about?
Just for starters.
Giving dates for things in the first place, more than a week or so in advance?
Letting people know what is being worked on?
Letting people know what bugs are being fixed, what content is being added, and what is not going to be fixed for a while?
People will argue that disclaimers cover their butts in all avenues (like those you listed), including communication. Of course, common sense dictates that this isn't true, and disclaimers are only their to cover their butts. They sure do not excuse poor communication with the community.
Of course, I think previews would be very nice and I hope it's something they could implement. I think it's the perfect use for the developer's blogs on this site. It's not something I'm particularly angry about though.
Can you point to a piece of communication in the last month or so that you think is cryptic? I'm interested in seeing a different point of view on this.I’m not angry. I guess being a business man I’m trying to understand the business or communications model. The communication yesterday, I understand that they didn't like what they saw after the update but what bugs were the problem, how long is the delay not we hope to get it up this week. Can we drop the bug fixes that are causing the problem, so the update can happen? That's why I think it would help if they had an active bug page (even if the fix didn't make into the next update they could show insiders the progress) that list bugs that have been fixed before the next update. Anyone can be angry but that doesn’t solve the problem. Plus I think at this point it would be best for Wotc to be as open as possible to win back trust.
The software developer in me cringes at this. If QA found some issues and a release is denied then they are having that exact discussion in house. I'll try to address your other points:
What bug(s) were the problem? Addendum: Can we drop those bug fixes so the update can happen?
I'm not sure that discussing either of these things is a smart move. They will make a choice to either do this or not for each issue that QA discovered. You've also assumed that the issues discovered are with bug fixes as opposed to problems with "new features".
How long is the delay?
This will be based on the decision made in the previous answer. Thankfully they have already answered this with "we hope this week". This also implies that they know what the issues are and expect to be done re-coding and testing said changes by then.
There was a drop off end of December when I was vacation, but that was explained and hopefully expected.
As to the level of communication people can expect: My goal is to come in at the beginning of the month and explain what's coming that month - including an update to the existing tools and whatever other information I have
When the update hits, I'll have a post that is also broadcasted and tweeted out that covers what was in the update, and what we can expect to see in the near future.
As for dates on that "near future" part, I don't think I'm going to be able to give those. I will get as close to a clear timeline as I can, but if I don't know a concrete date - I'm not going to give one.
And specific details about why we're doing something - I'm likely not going to give that either. Giving business decisions or detailed explanations of a technical issue that we had behind the scenes hardly ever leads to constructive conversations here. Of course, if there is an issue and I feel that we can have a constructive conversation if I'm able to hunt down answer's to the "whys" or the details of an issue, then I'll be back here with that information - but that is for specific exceptions.
So as I recap - I will try to give you a good idea of what you can expect, and a general idea of when you can expect it. That comes in one month updates and a general three month look ahead. Business decisions and internal issues will often remain internal unless there is a specific talking point where gathering constructive feedback will be helpful. Does that make sense and can people understand where I'm coming from on this?
Thanks Trevor. I really liked your post on the CB update today in that it included a list of planned future features for the product (a loose roadmap). I'm actually looking forward to the sharing characters feature for instance.
As I say nearly every time you post: keep it up! Some of us appreciate it. :p
Thanks Trevor. I really liked your post on the CB update today in that it included a list of planned future features for the product (a loose roadmap). I'm actually looking forward to the sharing characters feature for instance.
As I say nearly every time you post: keep it up! Some of us appreciate it. :p
I agree with Drnick today’s post had a loose roadmap. Trevor is there a list of the bug fixes for the CD update anywhere. I didn't start this thread to complain there are enough of those, just trying to get better information than what has been given. Great Start Trevor.
It is useful to see what features you plan to work on in the upcoming weeks, and hear about progress on the upcoming tools. Today's post on the update provided a good amount of this.
I would have prefered to get a more solid update on the AT, particularly since it seemed you were close to releaseing it last month. Now it seems unclear wither this will make it out next month.
Also, the only thing mentioned for the AT was the Monster Builder, it would be nice to know plans for other tools for the AT, if known.
Ed
Thanks Trevor. I really liked your post on the CB update today in that it included a list of planned future features for the product (a loose roadmap). I'm actually looking forward to the sharing characters feature for instance.
As I say nearly every time you post: keep it up! Some of us appreciate it. :p
I agree with Drnick today’s post had a loose roadmap. Trevor is there a list of the bug fixes for the CD update anywhere. I didn't start this thread to complain there are enough of those, just trying to get better information than what has been given. Great Start Trevor.
I dropped a quick post into the Character Builder forum about the bugs that were fixed in today's update, and I updated the main announcement about today's update with a link to that post. Let me know if you were looking for something else.
I would have prefered to get a more solid update on the AT, particularly since it seemed you were close to releaseing it last month. Now it seems unclear wither this will make it out next month.
Also, the only thing mentioned for the AT was the Monster Builder, it would be nice to know plans for other tools for the AT, if known.
Ed
I will have some information about the AT, very probably in the next couple of days. The reason I'm just talking about the MB is because that's all I know about at this point. When we get into beta, it will just be the MB - when I get more informatoin on other parts of Adventure Tools i'll definitely let you know.
I'll look for the addtional info on the AT when you can provide it.
I very much understand why you won't be commenting on business decisions and such, though of course I'd love to hear all that stuff whenever you CAN let us know!
Anyway, thank you so much, and keep it up. Many of us do very much appreciate it!
Why don't emailed "broadcasts" just simply tell me things?
Why do I have to:
1. Click a link in the email, which leads to a website
2. where I have to log in
3. Click yet another link, then, finally
4. Read a forum post?
Why, oh why, don't you just tell us at the beginning—in the email? Having to go through so many steps is significantly frustrating. I should say: was frustrating because I've stopped jumping through four hoops to listen to announcements.
Aside from being frustrating, it suggests that WotC doesn't know how to use the most basic internet communication, email, to do something useful: share information with people who want to hear it.
If I can't trust you to use email to communicate casual updates effectively, how can I trust you to tell me something that might be important?
A quick question:
Why don't emailed "broadcasts" just simply tell me things?
Why do I have to:
1. Click a link in the email, which leads to a website
2. where I have to log in
3. Click yet another link, then, finally
4. Read a forum post?
Why, oh why, don't you just tell us at the beginning—in the email? Having to go through so many steps is significantly frustrating. I should say: was frustrating because I've stopped jumping through four hoops to listen to announcements.
Aside from being frustrating, it suggests that WotC doesn't know how to use the most basic internet communication, email, to do something useful: share information with people who want to hear it.
If I can't trust you to use email to communicate casual updates effectively, how can I trust you to tell me something that might be important?
If I had to guess, this system is in place to try to keep this information available only to those privy to it (in this case DDInsiders.) If the DDI updates were placed directly into an email then it would be easily spread to numerous people it wasn't intended for. As to whether this is truly necessary I won't comment but I am sure many groups are glad for a layer of privacy.
If the DDI updates were placed directly into an email then it would be easily spread to numerous people it wasn't intended for.
No. You don't need to log in to see the updates so the information is already open and available to anyone.
It's only when you follow the link provided in the email do you have to log in. (Which only makes the entire thing more tragic.)
A quick question:
Why don't emailed "broadcasts" just simply tell me things?
Why do I have to:
1. Click a link in the email, which leads to a website
2. where I have to log in
3. Click yet another link, then, finally
4. Read a forum post?
Why, oh why, don't you just tell us at the beginning—in the email? Having to go through so many steps is significantly frustrating. I should say: was frustrating because I've stopped jumping through four hoops to listen to announcements.
Aside from being frustrating, it suggests that WotC doesn't know how to use the most basic internet communication, email, to do something useful: share information with people who want to hear it.
If I can't trust you to use email to communicate casual updates effectively, how can I trust you to tell me something that might be important?
For some reason the broadcasts disbale the hyperlinks. We're working with the platform providers to get that fixed up so you can click directly on the hyperlink to the forum post.
I don't duplicate the informatoin in the broadcast because if I need to change something in the forum post, I can do that with an edit. But if I mess up something in the broadcast, I have to send out a completely new broadcast.
Beta? Are you kidding me?
I will have some information about the AT, very probably in the next couple of days. The reason I'm just talking about the MB is because that's all I know about at this point. When we get into beta, it will just be the MB - when I get more informatoin on other parts of Adventure Tools i'll definitely let you know.
Beta? Are you kidding me?
Personally, I was very pleased with the communication in early Deecember, but it kind of degraded over the holidays to the point of being terrible again.
Throw a few breadcrumbs to sate the starving and promise that a feast is just around the corner... and then start baking bread for more breadcrumbs.
Yeah I noticed this too. the cancel the old CB and people freak out. then communication starts. people get happy that we get communication that we have been begging for for months and it starts.
Guess the cycle has to repeat before we get anything other then "more information coming soon".
Thanks for the communication Trevor it was nice to see information flowing. I know people are not happy about many of Wotc decisions (me included at times) but it was nice to see some response with effort behind it.
I dropped a quick post into the Character Builder forum about the bugs that were fixed in today's update, and I updated the main announcement about today's update with a link to that post. Let me know if you were looking for something else.
Thank you Trevor and all the Studio behind you. You're doing a good job. Keep feeding the channels !
I reviewed the bug lists and it was big. One thing i remarked. The Compendium and the CB carry changes to Powers that dont proceed into the proper channel of Rule Update, ex. 76. Duelist Prowess was added the Weapon Keywoord...
Can we expect to have another Rule Update sometime that will incorporate such changes ?
Merci !
Plague
What is it that's lacking right now, LightAngel? What communication would you like that you haven't received?
(I'm trying to make this into an actual conversation)
We are lacking the information on why were many products recently cancelled, what are the mid-to-long-term plans for 4th edition and are they going to publish any new classic 4e content (in addition to the occasional Dragon mag article).