Showing posts with label workbench. Show all posts
Showing posts with label workbench. Show all posts

Tuesday, January 2, 2024

Systematic Analysis of Opportunities is Vital to P-win's for Higher Proposal Win Ratios

Recognizing that not every identified Request for Proposal (RFP) is the right opportunity, the paper advocates for a systematic evaluation before committing valuable resources. The pre-bid-decision gap analysis, coupled with a Strengths, Weaknesses, Opportunities, Threats (SWOT) analysis, emerges as a potent hybrid approach. This method empowers businesses to assess internal and external factors influencing their ability to secure government contracts, fostering realistic expectations and strategic planning.

Bluedog outlines the crucial role of the gap analysis in the broader opportunity assessment process, emphasizing its integration into the RFP response cycle. By identifying gaps early on, businesses can enhance efficiency, optimize resource allocation, and minimize unnecessary work or rework. Ultimately, the pre-bid decision gap analysis emerges as a key driver of success, enabling businesses to navigate the complexities of government contracting with foresight and strategic acumen.

Get a PDF of the white paper here.



Tuesday, December 14, 2021

Automate More, To Increase Productivity. Makes Sense, But Why Don't Organizations Do That More Often?

 By now, most organizations should understand that automating processes does more than just make work go faster. Besides decreasing the overall cost to undertake tasks, workflow automation can help the staff avoid wasting their energy on repetitive tasks -- such as sending emails and following up on leads or generating documents. This frees them up to execute more productive and important tasks. 

Aiming to implement automation enables staff to avoid insignificant, repetitive tasks. They can shift their focus to value-oriented functions such as innovation in the development of new ideas and processes. Organizations that automate business processes change their workflows by reducing mundane activities and increasing team productivity. By automating business processes, companies can improve their processes, shorten business process cycle times, and maximize efficiency. The automation of processes completes tasks that were previously manual.

A good strategy for automating business processes can help maintain control over processes, reduce  errors, improve communication, and improve quality. Let's face it: repetitive and boring tasks can be frustrating, which leads to lower employee satisfaction. The use of automated processes in knowledge work processes can help a company produce higher quality deliverables and increase profits. For this reason, using technology to automate processes can help increase efficiency, productivity, and stabilize levels of quality control.

With tools that enable decision makers to monitor every step of the process without checking in with every employee, process automation enables staff to hone their precise role. The processes and tasks for which staff are responsible become streamlined, demonstrating one of the major benefits of workflow automation: it takes a lot of the pressure off staff. Think of when there are a lot of operational tasks that need to be done.

content creation workflow improves productivity

For example, when a team member needs to work through a list of ten items, chances are there are one or two tasks that one might dreading doing. When these tasks are automated, it provides relief for everyone and lightens the workload. Another great workflow automation benefit is that companies can hire more remote workers and keep their expenses down.



Thursday, July 30, 2020

Empower the Real Users of Software - with a No-Code Approach

Way back in the distant past, I used Hypercard, FileMaker, and, later, NeXT tools, to build complex expert systems, knowledge management, and financial planning tools for a diverse customer base. Applying a little bit of "MBA-powered" know-how with real-world entrepreneurialism enabled me to solve problems in the environmental sector, for small businesses, and even for the mortgage industry.

Fast forward to present day, and we see many software-as-a-service solutions that offer pre-packaged solutions to widely acknowledged challenges. My own solution for team management comes from a history of fixing broken projects for others -- I am a firm believer in the philosophy of "eat your own dogfood."

Now, we loop back to the past, with the increasing availability to low- or no-code software development solutions. Airtable, the Salesforce platform and web-based tools such as Ninox for databases are all useful tools to quickly assemble software to address highly specific problems. These are kind of the "spreadsheet" of the 21st century. One stand-out is Zapier, which has opened the door for many to integrate existing platforms with other popular web apps. Integrating applications with code can be a challenge, but Zapier makes it possible with a few clicks.

While no-code won't solve all technical challenges, having an easily accessible stack can undoubtedly help get specific jobs done faster, easier, and cheaper. Democratizing development is the overall benefit of no-code software development solutions. A few others include reducing the work load on an IT department, as such solutions enable business users to build applications without any coding knowledge. This reduces the burden on an understaffed IT department.

We can also enjoy an accelerated development cycle, so one doesn't have to wait for solution requests to be answered by theaters. Tasks that used to take months (even years) to complete can now be done in a few hours or days, depending on its complexity.

With many point-and-click user interfaces for the development of no-code solutions, one can quickly build solutions to meet exact requirements and specifications, and be updated on the fly. These aspects are important to keep the business competitive and agile. While a no-code solution allows the development of applications for immediate impact, it can also prove to be cost-efficient in the long run.


Tuesday, May 26, 2020

Read an Article about Group Problem Solving, Improved by Distance

From the BBC, we learn of the latest psychological literature suggesting that less communication might actually be better than constant inputs. Collaboration in an "always on" mode may in fact reduce ‘collective intelligence’ (a team’s joint problem-solving ability). Instead of always staying in touch with colleagues with continual chats on Slack, for example, the study suggests a better model would be to concentrate group communication to short, intermittent bursts – a single daily video call, for example – to boost team problem solving and creativity.

Besides helping us to make better use of our time during the current crisis, these findings could help to shape the ways that we go about team decision making in the future. Even if we are in the office, we might all benefit from having a bit more me time and a bit less team time.


Read more and download a PDF of the article.

Wednesday, September 4, 2019

Republic of Ireland Workers Have the Highest Productivity

In 2017, Irish workers crossed the line to becoime the most productive in the world, adding an average of $99.50 (€87) to the value of the economy every hour they work, according to the Organisation for Economic Co-operation and Development (OECD).


Read More... https://www.irishtimes.com/business/economy/irish-workers-now-ranked-as-most-productive-in-world-1.3783173

Friday, November 16, 2018

Create Diverse Workplaces Using Artificial Intelligence Ethically

Companies should be aware of and recognize that artificial intelligence algorithms are created by humans with biases and beliefs -- and make every effort to eliminate those biases.


A.I. takes input data and races off to make inference and decision making about the world at lightening pace,” --Dipayan Ghosh, a fellow at the Shorenstein Center on Media, Politics and Public Policy at the Harvard Kennedy School




Read more...

Friday, September 11, 2015

Queuing - Single Queue Works, But Why Doesn't Everywhere Do That?

Queuing theory utilizes applied mathematics to deal with the phenomenon of waiting -- arising from the use of mathematical analysis to improve production processes. So why doesn't McDonald's utilize this approach? Customer what times over 90 seconds can be problematic. But perceived wait time is more critical - like page loads in your web browser. If the UI/UX designer has come up with a novel way of loading content, a user will wait out the progress bar. Or, if the content is so compelling (think, your bank account, or cat videos).

But it helps to think of getting your french fry fix take-out as involving a series of work stations, each with a separate task. And each task takes time (e.g. ordering food, instructing workers, retrieving hot fries, putting into packaging food, payment). These stations are generally attended in sequence, and each station takes some time to process one customer. The sequence of stations is a pipeline. But some steps take longer than others -- so building in wait time at certain points actually serves to move the production process along without bottlenecks. McDonalds provides several queues in parallel, the first for ordering and paying, and the second, an (invisible) station where customers wait while their food is gathered and served. The time it takes to cook the food is accounted for in the time taken to gather the food items.

The same analysis can be applied to packet switching with internetworking, or with automobile assembly. For my masters work, I looked at a supplier to a Japanese auto manufacturer -- with a supply chain represented as a multi-input, multi-stage queuing network. An input order to the supply chain was represented by stochastic variables, for the occurrence time and for the quantity of items to be delivered in each order. I had seen such an approach when learning about the (now sunsetted) wide area network at the central bank, where I was involved with information security. A "star" network topology has a central top level node that all other nodes connect to. "Packets" are passed through the central node. This helped me understand alternate ways of queuing -- something I have carried forward with my efforts at automating workflow in Bluedog's SAAS offering, where 'jobs' have to be passed from one stage to another, based on business rules.

The typical first-come, first-serve system of waiting in line is incredibly inefficient, in terms of both time and space. First, it essentially rewards people for wasting their time: Those who arrive first get the goods, but they also spend more hours of their precious time on Earth standing around and waiting. Second, long lines tend to create congestion and bottlenecks that cause problems for others. Think of the traffic jams that form as cars try to leave a football game, or the long boarding line at an airport that snakes across the walkway, getting in everyone else's way.

Read more here... Danish Researcher Report or read this guy's ideas.

Thursday, July 10, 2014

The Virtue of Starting Fresh

Bluedog is working on a new version of its product, Workbench "Always on the Job!"© And we are facing new challenges everyday. It is great to be back writing code, and on the front lines of working with end users. This is how better mousetraps get built, IMHO.

When we opted to upgrade, we went around in circles at the beginning about Ruby vs WebObjects. About keeping legacy code as a base layer, or starting fresh. Ripping up the SDD and starting again is one of the hardest decisions to do even — especially when its your baby.

At other places I have worked, too many people have invested too much in an on-going project. There are too many stakeholders, too much institutional momentum. As a result, the impulse is to try to fix what is there.

When I got my MBA, one of the best things I learned — and embraced — is the concept of “sunk cost.” So, cleaning the white board made the most sense for Workbench 2.0 -- while cloud computing, n-tier MVC architecture, and the web are going strong, there are many exciting new opportunities in the world of software-as-a-service. And the economic turmoil recently has encouraged our customers evolve. So we have.

When Steve Jobs took over Apple again in the 1998, one of his first moves was to throw overboard projects that weren’t working – such as, the “Newton” handheld device (which, as readers may know, I loved). He started over, wanting a clean slate.

I am lucky — with the great team at Bluedog, I am able to ask, “If we were just to start fresh, what would we do?” That’s what we are doing, and I am excited to see us get to the launch pad!