The other week, we were approached with shuttling some of our content to a mobilized service. That service would basically take the RSS feed and then do some optimizations in order to make it work best for its platform.Well, we’ve got a lot of content here, and one of the items that came back to us was that we’ve got a lot of content and it makes it hard for them to figure out the best way to present our content. That’s a problem, but also speaks to the nature of the content here at MMM, and some of what has been happening behind the scenes to make the experience of reading the most relevant content more possible.
Developing The Firehose
Back when MMM got started online (April 2005), we had a model that was basically a copy of many of the high-traffic websites of the time: publish, publish, publish. I can remember at one point putting up 5-6 pieces a day, and many times unique pieces. For those not knowing what MMM was (amazing how folks stumbled upon us via a simple search), this wasn’t a bad thing. But over time, that got to be a bit much. We went to a single-post-a-day schedule many years back, and for the most part have been able to keep a consistent and constant stream of content flowing.
With that change in frequency came a change in the type of writing. I noticed from the analytics that the longer posts that we made had people stick around a bit longer. And not just to read that post, but they were most likely to go visit someplace else on the site. I shifted into making long-form content, best suited for contemplative reading – rather than quick skimming (other tech sites went this route) – but not to the length of what would be found on many theological sites (dissertations I tell ya). That change was also good for consistency, but a pain in the butt for organization.
The Battle to Organize Content
The move to WordPress from Blogger presented a chance to address some issues in terms of how content was organized on the site. At the time of that move, there were almost 3000 posts published and not quite a half of them were tagged/categorized. Google moved Blogger to a tagging system in the midst of our writing, and – well, its a lot of work to go back and retag content. I did a retaxionomy of the content based around some tighter editorial needs in that move to WordPress, and for the most part, its served us well.
What you might not have noticed is that some of those old posts from Blogger (see, http://archived.mobileministrymagazine.com) have been slowly making their way into WordPress. Unfortunately, the amount of content and structure of content wouldn’t import into WordPress, so each post has to be individually added to WordPress, retagged, and then categorized. That’s just something that will continue to take a while. In the meantime, there’s new content being produced that meets the current organizational schemes, in that long-form method, that’s usually quite unique, and generally posted on a consistent basis.
See the fun?
Steps of Manage the Firehose
Now, you would think that with some background in content management and information architecture that we probably shouldn’t be in this situation – but the fact of the matter is that MMM has changed over the years, as has its audience, as has the content. There are some streams of content not as often posted here anymore (direct software and hardware reviews), and there are others which tend to get much more the light of day (processes and UX matters). Where the content here becomes usable for you is in two offerings – based on the detail of the types of categorizing that happens here:
- Search
- RSS
Search is probably the most important (and most used) functional feature of this resource. Mainly because it is able to not only deal with the content that we’ve organized, but also dig a bit more into what we haven’t organized (thanks Google and WordPress). One of the pieces that is (unfortunately) missing from our mobile website is a suitable search interface (this is present on the alternate mobile website however). Not sure how and when that could be addressed on the mobile site, but its clear – at least from those of you who come here via Internet Explorer/Firefox/Safari that its a needed feature in terms of getting around.
RSS is the quieter feature used to manage the amount of content here. The way its used is actually a crafty by-product of the tags and categorization system present within WordPress. Every category and every tag points to a page that has its own RSS feed. This means, if you are looking at a subject area (perhaps Mobile in Missions/Evangelism for example) and you want to just get the updates for that stream of content only as it is published here, then all you need to do is either click on the RSS (orange colored) button in your URL bar, or take the URL for that page (http://mobileministrymagazine.com/tag/mobile-in-missionsevangelism/) and just add “feed/” to the end of the address and you have just the data stream for that page. Nearly every page has that functionality built in – and I’ve just not done a great job in talking about it.
The Missteps in that Firehose
The problem with things comes on some of our static pages (Bible apps, Case Studies, etc.) of which there is a listing of content, but those items are merely just a listing. There wasn’t a design to that set of data other than just putting it out there, making sure it linked to the right places, and sat under the correct subheading. That’s now biting MMM in the butt. Especially with the Case Studies/Resources page, there’s just an increasingly deep listing of content, and outside of searching on the page (click F3 on your keyboard if you are on a laptop and you can search within any single webpage), you just will have a hard time of finding what you are looking for.
WordPress is a decent content management system. However, making it work for this application (a multi-contextual listing of resources) would be stretching it a bit – even with extensions. The goal for each page is to be available, but to also be easy to manage. Until recently, that’s not been a problem. The query from the mobile services provider poked at that crack in the wall and we’ve got to figure something to do around it.
One of the solutions is to republish every resource and link on those static pages as a posting with their own set of categories/tags, and then build a custom page that would be able to contain those items. For those reading the blog, that’s going to be a lot of content coming through – and while some might be good to see, there are a lot of links to republish there. Another solution is to use the Links feature within WordPress, and then create a series of custom pages that would display those links as organized. Some of the work to do that has been started (in the background), but I’m still not sure what the final result will look like – though it will be a breeze to manage.
How You Can Help
As you can see, we are indeed aware of the amount and level of content that’s published here. Contrary to some opinions, we are quite focused as to what gets published and how it stays relevant to the overall purpose of this magazine. What we don’t know is how you engage the content here? That kind of information would help us better address what comes out of this hose, and how to continue to make sure what comes out is valuable. With that said, a few questions:
- Do you use a mobile app to view MMM? If so, which app(s) and why?
- Do you use an RSS reader to view MMM (which, why)?
- Do you use either the normal or alternate mobile websites?
- Do you use the email subscription via Feedburner to read content? If so, how do you archive, organize, resource those emails?
Thanks for your feedback on this. And if you have other ideas on how we can better manage the amount of content that comes here, do feel free to chime in via an article comment, the contact form, or Twitter (@mobileminmag)
One of the requests we’ve had out there for sometime is some testimonials, or case studies, in which those whom are building applications and services that service mobile and mobile ministry endeavors can be highlighted and lend some light to the depth and challenges in this space. A response came from a company, Enterra, whose 
We’ve recently added a new resource to our 
Over at Mobile Advance, a pretty wide/deep collection of articles from around the Internet have been pulled together into a spreadsheet and made available for review and analysis for those interested in those topics related to mobile ministry. If you’ve been a long-time reader of MMM (either the site or social networking) you’ll recognize many of the references in here. Here’s a snippet from the 
9(unknown*no*no*1)&guid=ON&x_utmac=MO-16595840-1){kind=small}
Mobile Ministry Methodology (v1)
Thursday, April 12th, 2012For the years that I’ve been looking at this intersection of faith and mobile technology through the lens of MMM, one thing has honestly escaped much of the conversation around the topic: if this intersection is valid, then what do people do to get past that intersection and into some relevant demonstration of their faith. In effect, what’s the method to the madness?
Being able to devote much more time to MMM in the past two (2) years has granted my thinking and action spaces to do just that – figure out the methods and some streams of activity within them. You’ve seen this in part if you’ve followed this site for sometime and watched its evolution. In this post, I kind of want to pull all of that together into what amounts into a mobile ministry methodology. The goal of this methodology is to literally demonstrate the definition of mobile ministry in the midst of practice and application.
What is A Mobile Ministry Methodology
The Mobile Ministry Methodology is a framework designed to assist individuals, ministries, and organizations determine the value, prospects, process, and successes of mobile ministry projects. Derived from SDLC methodologies, this framework is designed to keep the a singular goal in perspective despite tendencies for scope creep.
Please note, this is a framework. Therefore, activities within each phase might differ depending on the project. That said, the phases are quite rigid in keeping the focus of the project on both ministry and mobile applications.
Phase One: Determine if you are working on a mobile ministry project
The first step of this methodology is to determine if you are indeed working on a mobile ministry project. While it might seem that any project utilizing mobile devices and services is a suitable ministry project, the determining of whether it is a mobile ministry project falls towards whether the goals and activities within the project affirm the definition of mobile ministry:
(short version of definition)
If your answer to this question is that you are not working on a mobile ministry project, this methodology and process will not be helpful to you. If the goals of your project would like to line up with ministry, as well as keeping that technical component of being mobile, a good place to check the motives and goals of the project can be found using the following Biblical references:
Phase Two: Identifying the Frame for Mobile Ministry
There are several contexts in which mobile technologies have been used, or mobile behaviors tracked and observed. However, all of these are not specific illustrations of ministry (faith-building, faith-tradition extending, faith transformations can all be used as terms here). When mobile intersects with ministry, and the resulting actions are a change in behavior towards both technology and faith, then we can say that mobile ministry has occurred. MMM’s investigation and logging of activity in this space has identified these contexts (displayed here in their primary and secondary frames, linked to articles published here which correlate):
* These topics had their primary tag changed in the course of developing these articles; process is underway to normalize these.
Phase Three: Identifying the Primary Focus for Mobile Ministry Activity
Activities within the previously mentioned frames of mobile ministry have engaged in one or a combination of three focus areas:
Previous discussion on these.
The focus is determined by the core and learned competencies which area needed in order to direct the mobile ministry effort. Many mobile ministry projects will involve two or all three of these at some junction, but the primary focus clarifies how in the later steps you can better identify gaps, resources, and implementation items.
Whether you are using one or all three of these layers, it is helpful to have within your project person(s) which have specific knowledge of the devices and their capabilities, the programmable and political natures of the services to be implemented, and/.or then a definition of the experience for users, administrators, operators, developers, and any other stakeholders. Within these layers of mobility are a wealth of forks which will determine the success or failure of your project if they are not accounted for at this junction.
Engaging the Project Activities
Once you have identified the framing and focus, the methodology begins to take place. While this might look different for specific outfits, the software development lifecycle (SDLC) methodology actually grounds the following phases of the methodology/process:
Phase Four: Establish the Three Pillars
The first phase for the mobile ministry methodology involves what we call the three pillars: goals, issues, and resources.
This would be similar to the project initialization and analysis phases of an SDLC/Agile methodology. It is within your dissection of the issues and and resources in which an analysis of the feasibility of your project will come to light.
Phase Five: Design and Test
Design and Testing should happen in concert with one another. It will be clear after the identification of the goals and issues what exactly needs to be focused on. Design should therefore take place in two phases – staging prototypes/examples and test-ready prototypes/examples. I am personally of the opinion that you spend more time refining the design than testing multiple iterations, but I know of many people having different philosophies here. I’d also recommend that any design and testing (especially if we are talking applications, software, and workflows) should take place with live data, and not dummy data.
Testing is about whether you are making realistic steps towards your goal, and have you developed an experience with your product to match the expectations after that goal is met. Anything that you are testing that does not have direct correlation to solving the issues which prevent your goals from happening should be dismissed (or in some cases, lowered in priority). Testing should also be designed to correspond to the availability of your resources in concert with how the results of the testing knock off all or some of the issues raised in the previous phase. There is potential for projects to spoke into additional requirements or opportunities as a result of the testing/testing data, so I would recommend that anything learned that does not positively effect your specific goals, be dropped for another project or future iteration of the current project.
The testing scripts should be designed so that they can be used in the Post-Implementation phase for reporting and support needs.
Phase Six: Implement
Implementing a mobile ministry project can be a difficult proposition. If this is an application, implementation might look like a slow-beta period, or a larger “let’s see what happens” kind of release. When it is a business process, implementation cannot afford such slow releases, and usually includes additional time and resources towards addressing items that could not show up in testing, implementing training, and finishing the reporting queue.
Your public feedback queue and media channels should be established and utilized at this point. Mechanisms such as Twitter, Facebook, Get Satisfaction, etc. are excellent for acquiring and monitoring specific feedback, while also lending a (hopefully) positive light on your ability to manage the roll-out of your product.
Phase Seven: Support, Report, and Reinitialize
Supporting your product includes having the appropriate documentation (text, video, etc.), publicity support, and consistent presence (support forums, email channels, etc.) which allow you to take in and categorize compliments and issues related to the implemented iteration of your project. Support does not necessarily include fixing all of those items which are brought to your attention – some items need to be input into the queue for re-initialization into another project.
As with your testing queue, the reporting structure that you use to watch usage, trends, and spot potential problems down the line should be in place here. Your report data might come from server logs, emails, or a combination of several streams of data, to which are collected in a regular report by which project managers an stakeholders can have a concise view of the project as it related to the specific goal.
Reinitialize means that you’ve met enough the goals of your project, and due to the data gained within the design, testing, implementation, or support/report streams, that you have an update to the project that you can do. Again here, the goal needs to be specific, but also not deviate greatly from the original product’s goal. It is not uncommon to go back to the drawing board and rebuild at this point.
Review of the Mobile Ministry Methodology Phases
View these phases in a graphical process map:
This process map was created in Google Docs for collaborative purposes. The Google Docs version will always be the latest iteration of this.
Items Not Seen In this Methodology
This methodology has been designed to be very generic. How you or your team manages their tasks, template documents, or other assets is not the point of this methodology. It is a framework to assist you/your team to understand from the outset of the project how to focus your efforts without losing focus of the faith and technological implications of your product. If at the end of your project, you have clearly demonstrated that you have forwarded some/all of the key ideals or behaviors of your faith tradition, then you can successfully say that you have engaged within mobile ministry.
If you have any comments or questions towards this methodology, please do not hesitate to email or send a message via Twitter. Its my expectation that this methodology will enable groups, such as those involved within the Mobile Ministry Forum, better identify successes, challenges, best practices, and other aspects of mobile ministry that have been hard to define and implement.
Associated Resources
Tags: best practices, definition of mobile ministry, flow chart, layers of mobile, methodology, Mobile in Analytics/Marketing/Development, Mobile in Discipleship/Education, mobile in media, mobile in missions/evangelism, mobile in personal/moment, mobile in spiritual/theological/psychological, process, process flow, resources
Posted in Commentary | No Comments »