ThoughtWorks
  • 联系我们
  • Español
  • Português
  • Deutsch
  • English
概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

    智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 低摩擦的运营模式

    提升组织的变革响应力

    企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

    合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
概况

特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
  • Español
  • Português
  • Deutsch
  • English
ThoughtWorks菜单
  • 关闭   ✕
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们
  • 返回
  • 关闭   ✕
  • 概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

  • 低摩擦的运营模式

    提升组织的变革响应力

  • 智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

  • 企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 返回
  • 关闭   ✕
  • 概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
  • 返回
  • 关闭   ✕
  • 概况
  • 特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

  • 数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

  • 所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

  • 返回
  • 关闭   ✕
  • 概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

  • 返回
  • 关闭   ✕
  • 概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
博客
选择主题
查看所有话题关闭
技术 
敏捷项目管理 云 持续交付 数据科学与工程 捍卫网络自由 演进式架构 体验设计 物联网 语言、工具与框架 遗留资产现代化 Machine Learning & Artificial Intelligence 微服务 平台 安全 软件测试 技术策略 
商业 
金融服务 全球医疗 创新 零售行业 转型 
招聘 
职业心得 多元与融合 社会改变 
博客

话题

选择主题
  • 技术
    技术
  • 技术 概观
  • 敏捷项目管理
  • 云
  • 持续交付
  • 数据科学与工程
  • 捍卫网络自由
  • 演进式架构
  • 体验设计
  • 物联网
  • 语言、工具与框架
  • 遗留资产现代化
  • Machine Learning & Artificial Intelligence
  • 微服务
  • 平台
  • 安全
  • 软件测试
  • 技术策略
  • 商业
    商业
  • 商业 概观
  • 金融服务
  • 全球医疗
  • 创新
  • 零售行业
  • 转型
  • 招聘
    招聘
  • 招聘 概观
  • 职业心得
  • 多元与融合
  • 社会改变
体验设计技术

The 3-lens approach to agile design

Nate Argosh Nate Argosh

Published: Nov 6, 2020

A mental toolkit for prioritizing and designing.

Facing a mountain of work as a one-person design team is daunting.

In startup and consulting environments, often a sole person becomes responsible for work that may otherwise be divided amongst product designers, product managers, UX designers, researchers, interaction designers, the list goes on. The vast array of online design communities contain fantastic resources for championing design or prioritizing features but concrete workflows and processes seem to be locked in secrecy.

The world loves to talk about agile and what it means for software development but many seem to elude the ever-present question of, “what should I be doing today so that I don’t cause a catastrophe tomorrow?” This piece presents a generalized approach to prioritizing daily design work as a one-person design team in a fast-paced, agile delivery environment.

The Lenses

Most products are alive, constantly being shaped and molded as the end user’s needs evolve. Rather than discussing project inceptions or closures, this approach addresses the ongoing design tasks associated with delivering software — the daily grind.

All feature work is seen through one of three lenses: the far, the near, and the immediate. As a piece of work moves from a fuzzy idea in the distant future to a pixel-perfect story card awaiting kick-off, it travels through each lens’ field of view.
  • The far lens is like putting on binoculars. User research is conducted, and high-level decisions are made about the future of the product. The goal here is to ensure you’re building the right things.
  • The near lens is like a pair of reading glasses. User stories are prioritized and thoughtfully researched to prepare for the final leg. The goal here is to ensure you’re building the thing right.
  • The immediate lens is like a magnifying glass. The goal is to have a smooth kick-off and avoid re-work. Rework consists of bugs, and unclear requirements; it slows down projects dramatically.
A feature moving through the three lenses
Not only is it important to know when to move work from one lens to another, but also what design work looks like in each lens. Performing design activities that are too specific, too early could result in wasted time. Requirements can change as a feature nears closer to development.

The three lenses require three different modes of thinking. While the far is abstract and creative, the immediate is meticulous and analytical. Context-switching can become exhausting, so the ever-present challenge of time management is of the utmost importance. In the following sections I try to explain when to pick up the magnifying glass vs the binoculars. 

Design work evolves from a fuzzy insight to a clearly defined story

The Far 

Work in the far lens is blurry and often distant. In the far one should constantly question the motive behind features. Does the user want this? If they do, does the business have anything to gain by supplying it? User research takes priority, then synthesizing user research, followed by brainstorming and exploratory prototyping.

Work in this lens is kept in exploratory prototypes and user research findings. The tools of choice for tracking work may be a product roadmap and user research insights (a great method for documenting user research). Work in the far may be implemented in four weeks, or maybe in a year. In order to move work from the far to the near, one must ensure that the feature drives the product towards a business objective by addressing a real need of the end user.

The Near 

Generally, by the time a feature moves to the near it has been divided into stories. In the near, the story is opened up and explored. Key features of the story are illustrated and documented while loose ends are tidily capped. The tool of choice for tracking work may be a story map.

While looking through the near lens, internal and external stakeholders should be tracked down to iron out legal restrictions, data assumptions, privacy concerns, and technical implications. The information architecture of the page is validated, and the functionality of every button is confirmed. The designer should position themself with all the knowledge they need, document it, and leave once they’re confident their handwriting is legible.

The Immediate 

Once a story is prioritized and it’s about to enter centerstage, it’s moved to the immediate. By the end of the story’s journey, the designer should be confident they have sufficiently researched and documented to instill a shared understanding with developers at kick-off. The story kick-off is a vital ritual to ensure developers are equipped with all the knowledge they need to flawlessly implement the story.

In the immediate, stories are dissected. Every word on the error message is correctly capitalized and every icon is exported for handoff. The tool of choice for tracking work may be a Kanban board or a story wall.

In Practice

When working on a small software delivery team, there’s usually one clear bottleneck: development. Designers can move shapes around on a mockup all they want, but it takes time for developers to work their magic. It’s imperative that as soon as a developer pair finishes a story, there’s a new story sitting on the conveyor belt for them to assemble. This is why every morning the magnifying glass should be picked up first to ensure the next set of stories are ready. Then move to the near to ensure the next batch of stories are prioritized and ready to be moved. Only then are the binoculars picked up to examine the far.

This is the piece that some find counterintuitive: while

features move from the far to the immediate, designers

should move in the opposite direction.

The secret sauce to formulating a well-weighted day is found in the team chemistry. Constant communication with the team lets designers gauge the velocity of developer pairs. Suspecting a pair has a couple of large tasks ahead of them which are pre-packaged and ready to begin, the day is suddenly free to interview users or reorganize the roadmap.

I’ve been slowly developing this approach but the thoughts all came together during a recent project when I was the sole designer responsible for all of the product, design, and much of the project management. I hope this methodology supplies you with a mental toolkit to prioritize work and approach it at the appropriate level of detail.

Gone are my days of 10 AM paralysis, spending so much time determining what to design that I design nothing. Scanning back through my calendar, I can see my tasks cleanly divided into the three lenses, and as I sit down to compose my thoughts, I realize I would have been lost without them.
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们

WeChat

×
QR code to ThoughtWorks China WeChat subscription account

媒体与第三方机构垂询 | 政策声明 | Modern Slavery statement ThoughtWorks| 辅助功能 | © 2021 ThoughtWorks, Inc.